2e59a8c0 8345-479d-b6ef-5c6529a62d83 on 14 Sep 2016 13:09:18
Add security to show/hide any specific page (Tab) on a report based on users privileges / Roles.
Phanidhar Bobba (administrator) on 21 Jun 2023 09:23:12
Thanks for all the feedback! We'll consider this feature for a future release but no timelines to share just yet.
- Comments (424)
RE: Page (Tab) level Security.
Following ..Its a must!!
RE: Page (Tab) level Security.
It's function very helpful. Please consider to build this. Please advise me When You have any idea about security to show/hide ant page on a report.
RE: Page (Tab) level Security.
Would be very helpful. This way we do not have to create multiple reports that have the same data imports.
RE: Page (Tab) level Security.
Waiting for it!
RE: Page (Tab) level Security.
Clearly must-have functionality.
Would allow to have only one dataset/workspace to share with a whole organization but with ability to show certain reports/KPI only to a group & not the whole group.
That could be done by attributing tags or roles to tabs information panel --> if a tab is tagged for role XXX then this role can view it. If not tagged, the tab do not appear to the user.
RE: Page (Tab) level Security.
We have certain tabs that show nothing because the row level security blocked all the data on that page. It would be nice if we could just hide the page as well based on role. Thanks for considering.
RE: Page (Tab) level Security.
This is a great idea
RE: Page (Tab) level Security.
We have multiple datasets in seperate workspaces and resulting apps. The Role Level Security is very time consuming.
1 We set the Roles (100+) on each dataset in the desktop - could it be possible to create a copy feature from one dataset to another.
2. We assign the users to roles within the security in each dataset on the Service - could this be eliminated by creating an AD style master to all the Services where the user is assigned to role just once at a master level and this is then links the users under SSO to limits based on the role security set at the desktop level (instead of having to do it on every dataset that gets published to the server)
3. When we publish App we again have to enter ever users email we want to have access, could be simply assign a group of even better user a multi select tick based on all user roles that have been set up in the master user control in step 2 above.
RE: Page (Tab) level Security.
We have certain tabs that show nothing because the row level security blocked all the data on that page. It would be nice if we could just hide the page as well based on role. Thanks for considering.
RE: Page (Tab) level Security.
Very important for our business as well!