Participant Level Features
Best Answer
-
McSwag,
The features you've described are not currently available with publication groups. There have been a lot of upvotes on the post in the ideas exchange about this and the product team is looking into it.
In the meantime, I want to clarify something about PDP that might make things work out better for you. There is no problem with using PDP on the output of a dataflow. It just shouldn't be used on an input to a dataflow. What this means is that whatever dataset you are using to power the cards on the page you are using for your publication group could have PDP applied unless you are using it as an input to another dataflow as well. Switching to PDP instead of publication groups would give your users the ability to favorite and create alerts on the cards you share with them.
Here's the link to the existing idea:
From the thread it appears that this may be coming soon.
2
Answers
-
Are you using publication groups or PDP to limit/distribute content? We had the same issue when we used Publication Groups to distribute. Since moving to PDP Favorites, Alerts etc. are available to all users.
0 -
Hi McSwag,
A user with "Participant" level access should be able to do both of those things. For your reference here is an article containing a matrix with user security roles that lists their permissions:
http://knowledge.domo.com?cid=understandingsecurityroles
Are you certain your user has "Participant" level access?
0 -
I was unclear: meant can we do this when the participant has their data filtered via publication groups.
Because we are utilizing DataFlows, PDP is not a viable option. Our participants cannot set alerts or favorite cards that are filtered via the publication group.0 -
McSwag,
The features you've described are not currently available with publication groups. There have been a lot of upvotes on the post in the ideas exchange about this and the product team is looking into it.
In the meantime, I want to clarify something about PDP that might make things work out better for you. There is no problem with using PDP on the output of a dataflow. It just shouldn't be used on an input to a dataflow. What this means is that whatever dataset you are using to power the cards on the page you are using for your publication group could have PDP applied unless you are using it as an input to another dataflow as well. Switching to PDP instead of publication groups would give your users the ability to favorite and create alerts on the cards you share with them.
Here's the link to the existing idea:
From the thread it appears that this may be coming soon.
2 -
From what I understand, I believe the long-term intent is for data fusions to inherit their pdp policies from parent datasets (we have one dataset that determines all pdp policies). I'm told some time between now and the user conference this should be up and running. We've enjoyed data fusion for simple joins as it runs much faster than all other options in DOMO, but the no pdp piece is a drawback.
1 -
a drawback indeed.
0
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