Allow certification of published content in subscriber instances

After certifying content in a publisher instance, it would be convenient to have that content arrive in the subscriber instance pre-certified.
A more effective publishing setup would allow the sync/update of certification policies between instances so certified Domo content can retain certification through publishing.
This would improve the reach, impact, and visibility of certified content, as well as cut down the amount of admin required to manage certification, especially if there are a lot of subscriber instances.
Comments
-
@DInwood - Can you tell me about your pub/sub setup? Are you using it in a "enterprise" situation where you are publishing between instances which all "belong" to the same company? Or are you publishing to 3rd parties?
I ask, because publish has many ways it's used - for example, 2 distinct organizations could use publish to do some kind of datasharing agreement, in which case published content while "certified" by the provider, may not be yet trusted by the recipient. We might need some way to have both a "certified by publisher" and "certified by recipient" to address this request.
Cadell Falconer
Principal Product Manager0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 307 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 112 SQL DataFlows
- 649 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 790 Beast Mode
- 78 App Studio
- 43 Variables
- 745 Automate
- 187 Apps
- 475 APIs & Domo Developer
- 67 Workflows
- 16 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 406 Distribute
- 117 Domo Everywhere
- 279 Scheduled Reports
- 10 Software Integrations
- 139 Manage
- 136 Governance & Security
- 8 Domo Community Gallery
- 47 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive