Customize dashboards for different reporting personas using PDP
I created a unique dashboard that is meant to be used by different reporting personas. We chose the persona with the highest access level to define the cards and their drill-down views.
Then, we applied customized PDP according to the other reporting personas (manager, department director, etc) to all datasets that power the dashboard.
My question is: using PDP, could we remove from the dashboard those cards that are not meaningful for a particular low-access level reporting persona as well as certain drill-down views without altering the original dashboard? Currently, I remove access from a card to a specific Domo user (associated to a reporting persona) through the "Admin setting", removing a specific card from the "Access to Content -> Cards" section, but this doesn't work for drill-down view. Any idea on how to customize a unique darsboard for different reporting personas?
Best Answers
-
Hi,
Removing cards or drill downs isn't something that you can use PDP for. All PDP does is restrict access to the data, it has no impact on the cards or drill downs.
It sounds like the current process your using to customize the dashboard by removing access through Admin settings isn't ideal. I'm not completely sure how many personas you have nor how many users that fall into each persona but one thought I had was to have different subpages for each persona, then you don't have to worry about having blank cards/drill downs because you could customize it for each persona.
So for example you'd have one subpage called "Executive" or something like that which would have all the applicable cards. Then you'd have another called "Manager" which would probably have less cards, or maybe just different cards and so on with the other personas. The underlying data is still protected by PDP and then each user get's a customized experience with the dashboard only poplulated by cards & drill downs applicable to their role.
Hope that helps!
1 -
For what it's worth, we have pages for personas as well as PDP/Publication groups in place.
The execs have their page and can see everything.
The managers have their page, with slightly different cards, and can only see their own segment.
The reps can see the reps page, again with slightly different cards, and can only see their own, individual values.
We've found, for our case anyway, that these audiences/personas often don't want or need to see exactly the same information presented exactly the same way as the other groups, so the dashboards really end up morphing into different dashoards over time anyway.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"2
Answers
-
Hi,
Removing cards or drill downs isn't something that you can use PDP for. All PDP does is restrict access to the data, it has no impact on the cards or drill downs.
It sounds like the current process your using to customize the dashboard by removing access through Admin settings isn't ideal. I'm not completely sure how many personas you have nor how many users that fall into each persona but one thought I had was to have different subpages for each persona, then you don't have to worry about having blank cards/drill downs because you could customize it for each persona.
So for example you'd have one subpage called "Executive" or something like that which would have all the applicable cards. Then you'd have another called "Manager" which would probably have less cards, or maybe just different cards and so on with the other personas. The underlying data is still protected by PDP and then each user get's a customized experience with the dashboard only poplulated by cards & drill downs applicable to their role.
Hope that helps!
1 -
Thanks for your message. We thought about this option as well, but ideally we would like to maintain only one collection of cards (a single sub-page) since creating different sub-pages for each reporting persona potentially would make the maintenance process more complex and arduous. However, I see the value of creating different sub-pages for each reporting persona and this might be the way to go, specially because when you copy a card in two different sub-pages and modify one of them, the modifications are present in both cards.
Thanks for the input pnce again!
1 -
For what it's worth, we have pages for personas as well as PDP/Publication groups in place.
The execs have their page and can see everything.
The managers have their page, with slightly different cards, and can only see their own segment.
The reps can see the reps page, again with slightly different cards, and can only see their own, individual values.
We've found, for our case anyway, that these audiences/personas often don't want or need to see exactly the same information presented exactly the same way as the other groups, so the dashboards really end up morphing into different dashoards over time anyway.
Aaron
MajorDomo @ Merit Medical
**Say "Thanks" by clicking the heart in the post that helped you.
**Please mark the post that solves your problem by clicking on "Accept as Solution"2 -
Thank you all for your input. I think creating a sub-page for each reporting persona seems to most appropriate and scalable solution to this use case. I will test it out in the following days. Thanks!
1
Categories
- All Categories
- 1.8K Product Ideas
- 1.8K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 297 Workbench
- 6 Cloud Amplifier
- 8 Federated
- 2.9K Transform
- 100 SQL DataFlows
- 614 Datasets
- 2.2K Magic ETL
- 3.8K Visualize
- 2.5K Charting
- 729 Beast Mode
- 53 App Studio
- 40 Variables
- 677 Automate
- 173 Apps
- 451 APIs & Domo Developer
- 45 Workflows
- 8 DomoAI
- 34 Predict
- 14 Jupyter Workspaces
- 20 R & Python Tiles
- 394 Distribute
- 113 Domo Everywhere
- 275 Scheduled Reports
- 6 Software Integrations
- 121 Manage
- 118 Governance & Security
- Domo Community Gallery
- 32 Product Releases
- 10 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 108 Community Announcements
- 4.8K Archive