During the Developer Launch period, you can request to have your connector listed in the Data Studio in-product Gallery as well as the public gallery. Users will be able to add and use your connector from either gallery.
To publish your Community Connector, it needs to be reviewed. If approved the connector will be included in the galleries. You need to complete the following tasks to publish your connector.
Enable link sharing for your connector project
Enable link sharing for the project to provide read access.
Complete and validate the manifest file for your connector
Update the manifest file following the manifest reference. Ensure that all assets and resources mentioned in the manifest, including logo, support URL, addon URL, company URL, and templates are available and can be publicly accessed.
Review Terms of Service
You and your connector need to adhere to the Data Studio Galleries Terms of Service (Submitter).
Submit your community connector for publishing
Complete the Community Connector Publishing form to submit your connector for review. In addition to the information in the manifest, you will need to provide the deployment ID and the link to your project for the review. Note that if you are publishing multiple connectors, you will need to complete the form separately for each connector.
The review process might take from a few days to a few weeks. If your connector is approved, you will receive a notification and the connector will be added to the Community Connector Gallery. If your connector does not pass the review process, you will be notified of the shortcomings and guidelines for resubmission.
Remove your community connector from the gallery
To remove your Community Connector from the gallery, send a removal request to firstname.lastname@example.org.
Best practices for publishing your Community Connector
- If your connector connects to a paid service
- Indicate in the description that it is a paid service / connector.
- Provide a trial option. The link to signup for the trial should be visible during the authorization or configuration screen.
- Clearly communicate to the users the limitations of free usage, if any.
- Provide sample data if possible.
- Provide report templates.