我是否必须公开提供自己的社区可视化图表代码?
您的代码需要能够公开读取/访问。这并不是说您需要公开宣传或共享自己的代码,而是应假设对于使用您的社区可视化图表的报告而言,任何查看者都可以查看您的可视化图表代码。与任何人共享组件 ID 的情况也是如此。他们将能够加载社区可视化图表并将其添加到自己的报告中。未来我们可能会提供一些选项,支持不公开或经过身份验证的社区可视化图表。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eLooker Studio's Community Visualizations empower users to create and integrate custom visualizations into their reports.\u003c/p\u003e\n"],["\u003cp\u003eThis Developer Preview offers core functionalities and resources for building, sharing, and managing visualizations using the Looker Studio Community Component Library.\u003c/p\u003e\n"],["\u003cp\u003eUsers have control over enabling/disabling Community Visualizations within their data sources, ensuring data security and flexibility.\u003c/p\u003e\n"],["\u003cp\u003eWhile external resource requests are currently restricted for security, future development plans include enhancements to developer workflow, distribution options, and new visualization capabilities.\u003c/p\u003e\n"],["\u003cp\u003eFeedback is encouraged to shape the future of Community Visualizations; users can stay updated through the changelog and submit feedback via designated channels.\u003c/p\u003e\n"]]],[],null,["# Community Visualizations Developer Preview\n\nCommunity Visualizations allow you to build and use your own\nvisualizations in [Looker Studio](https://lookerstudio.google.com). The Developer Preview / Beta introduces the\ncore functionality, resources, and tools required for you to build and share\nvisualizations in Looker Studio.\n\nDeveloper preview\n-----------------\n\nThe Developer preview launch includes the following:\n\n- The Community Visualization feature is enabled for all users. Anyone can build and use visualizations. See [Getting started with community visualizations](/looker-studio/visualization/get-started).\n- The [Looker Studio Community Component Library](/looker-studio/visualization/library) is available. The helper library makes it easier to develop community visualizations.\n- Community Visualizations can be published in the showcase. Find out how to [share your visualization](/looker-studio/visualization/sharing).\n- A Data Source control is available to turn Community Visualizations on/off. By default, Community Visualizations are turned on for a data source but consent is required when adding a visualization to a report. Learn how to [Enable community visualizations in your data source](https://support.google.com/looker-studio/answer/9206527).\n\n| **Note:** \"Developer Preview\" means the feature is stable and ready for developers to build and use visualizations in reports. It's intended to give all developers access to explore the feature and an opportunity to provide [feedback](/looker-studio/visualization/support) to make Community Visualizations even better.\n\nPartner Visualizations\n----------------------\n\nPartner visualizations go through a review process, and are featured as part of\nthe in-product gallery in Looker Studio. The Partner Visualization program\nprovides:\n\n- In-product visibility\n- Opportunities for promotion through communication + social channels\n\nTo participate and publish your visualization:\n\n1. [Build a visualization](/looker-studio/visualization/get-started)\n2. [Submit](/looker-studio/visualization/publish) your visualization to the gallery.\n\nWhat's next\n-----------\n\nThe Developer Preview sets the foundation from which you can build and use\nCommunity Visualizations. However, there is an extensive roadmap that will\nimprove the experience for developers.\n\nSome of the features and improvements under consideration:\n\n- **Development**\n\n - Improving the developer workflow.\n - Supporting more advanced data and style configuration options.\n - Better control over deployments and pushing new changes.\n- **Distribution**\n\n - More options to publish your visualization/components for other Looker Studio users to discover and use in their reports.\n- **New capabilities**\n\n - Performance improvements.\n - Additional controls for users and developers to manage visualizations and to decide which visualization(s) can access external resources.\n\n| **Note:** This list is subject to change, depending on feedback.\n\nStay up-to-date and provide feedback\n------------------------------------\n\nTo stay up-to-date on changes such as fixes, improvements, and new features\nfollow the [changelog](/looker-studio/visualization/changelog).\n\nWe would like to hear from you! What's working well for you, what isn't,\nand what features or improvements would you like to see? To provide feedback to\nthe team see [Sending feedback](/looker-studio/visualization/support).\n\nFAQ\n---\n\n**Do I have to make my community visualization code public?** \n\nYour code needs to be publicly readable/accessible. That doesn't mean you need\nto promote or share it publicly, but you should assume that any\nviewer of a report that uses your community visualization can view your\nvisualization code. The same is true if you share the component ID with anyone.\nThey will be able to load and add your community visualization to their reports.\nThere may be options in the future to allow for private or authenticated\ncommunity visualizations.\n\n**Where do I report an issue or request a feature?** \n\nIf you've discovered an issue, first review the list of\n[Limitations / Known issues](/looker-studio/visualization/issues) to determine if this is a known issue.\nYou can submit feature requests and issues by following the instructions for\n[Sending feedback](/looker-studio/visualization/support).\n\n**Why can't my visualization make requests for external resources?** \n\nThere is a [Content Security Policy](https://en.wikipedia.org/wiki/Content_Security_Policy) that restricts requests for external\nresources. This is in place to mitigate the risk of a community visualization\nsending data to an external server.\n\n**Why can Community Visualizations be disabled by the data source?** \n\nEven though a [Content Security Policy](https://en.wikipedia.org/wiki/Content_Security_Policy) restricts requests to external\nresources, some users prefer to know that their data will never be rendered by a\nthird-party built community visualization. The data source setting\ngives users the option and assurance their data will never be rendered by a\nCommunity Visualization.\n\n**I created and trust my own visualization, why can't my code make requests for\nexternal resources?** \n\nFor now the [Content Security Policy](https://en.wikipedia.org/wiki/Content_Security_Policy) is enforced for all\ncommunity visualizations. However, there may be options in the future to relax\nthis for special circumstances.\n\n**Can I monetize my visualizations?** \n\nYes. However, in order for your community visualization to work there is\ncurrently a requirement that all resources are public. There are also no\nauthentication services in place to prevent anyone from using your\nvisualization. Monetization options are not a priority during developer preview,\nbut in the future there may be better options available to support this use\ncase.\n\n**Can I make my Community Visualization source code public?** \n\nYes, it's up to you. If you are interested in open sourcing your visualization\nsee [Sharing](/looker-studio/visualization/sharing). There is no requirement for\nyou to publish your source code."]]