Restricting certain columns of sensitive data in Public accessible dashboard
I'm interested in sharing some dashboards with agencies via the embedding dashboard option. However, I'm a little confused how I can set this up. I see two different options:
I can make a dashboard private and only allos users to authenticate from a Domo account (which obviously wouldn't work in this case) or API…. would the API just be for pulling data? Or is there a way to allow agencies to access the dashboard via an API we exclusively proivde?
If I go with the public option… I see there is away to block access to sensitive columns by either deactivating the interaction option or by transforming the data to exclude those columns. How do I apply the interaction option to prevent certain columns from appearing in public links? For the transforming the data by excluding columns option, I assume this would be for all dashboards (there isn't a way to dynamically exclude columns if they are being viewed via a public link, is there?)
Best Answers
-
Hi Nathan,
I don't have experience of embedding dashboards. But did you try applying PDP to your dataset columns that you wouldn't want to appear for public view? Ideally, it PDP should also apply to the dashboard or other elements where you're sourcing this dataset…
0 -
There is "Domo Everywhere", where you can privately embed instances of your dashboard somewhere outside of Domo, and it is possible to create your own authentication with that private embed (i.e. not a Domo account). Using Domo Everywhere does cost more and there are technical hurdles to implementing it.
PDP is not available for Public Embed:
A different approach for public embed is you could feed your dashboard (or a copy of your dashboard designed for this use case) using a "view" of your data, where that view only has the columns/rows you feel comfortable sharing publicly.
Please 💡/💖/👍/😊 this post if you read it and found it helpful.
Please accept the answer if it solved your problem.
0
Answers
-
Hi Nathan,
I don't have experience of embedding dashboards. But did you try applying PDP to your dataset columns that you wouldn't want to appear for public view? Ideally, it PDP should also apply to the dashboard or other elements where you're sourcing this dataset…
0 -
There is "Domo Everywhere", where you can privately embed instances of your dashboard somewhere outside of Domo, and it is possible to create your own authentication with that private embed (i.e. not a Domo account). Using Domo Everywhere does cost more and there are technical hurdles to implementing it.
PDP is not available for Public Embed:
A different approach for public embed is you could feed your dashboard (or a copy of your dashboard designed for this use case) using a "view" of your data, where that view only has the columns/rows you feel comfortable sharing publicly.
Please 💡/💖/👍/😊 this post if you read it and found it helpful.
Please accept the answer if it solved your problem.
0
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 300 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 616 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 731 Beast Mode
- 55 App Studio
- 40 Variables
- 682 Automate
- 175 Apps
- 451 APIs & Domo Developer
- 46 Workflows
- 10 DomoAI
- 35 Predict
- 14 Jupyter Workspaces
- 21 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 122 Manage
- 119 Governance & Security
- 8 Domo Community Gallery
- 38 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 107 Community Announcements
- 4.8K Archive