Being able to hide pages in the new UX based on role, not just selective access, in a way similar to Contents for the classic UX would help control user access so that users don't see pages that aren't relevant to their needs.
I agree. Some way to customize page/app access by role/user is critical for our business. Otherwise, we will need to redesign a lot of our model architecture in order to drive security purely based on access to underlying modules, rather than simply showing/hiding pages from a user's settings.
@daian , @DavidEdwards I think is already delivered. You can restrict the pages based on the roles using "Page Options"-> "Restrict Access" from the design mode of a page.
However, you do not have a nice interface as "Content" like where you have a matrix between pages and roles to have a general view of this.
You need to do it page by page... Maybe this interface can be improved.
Thanks, @alexpavel! I agree. I think this was delivered at some point since the original post was made, and it fits the need for restricting access.
Thanks @alexpavel. That is very helpful. It would be very nice to hide full pages from the App view by user role (vs. having to click into it before finding out you do not have access). Does anyone know of a way to do this? Thanks, JZ
Hi,
Is there news on this issue? I have three home pages depending on the role
Regards
We got several hundred of modules. I think it could be usefull if modules can get sorted/filtered by (dynamic) groups or even in folders in the modules overview. Maybe the Data Tags could used with this. //GP
Selective Access for list used as a format of line item works properly when given line item is published on dashboard or page. Unfotunatly if user wants to filter data manually, he/she is able to see all items from the list. This behaviour was observed on dashboards and in NUX as well. This issue is most troublesome for a…
While working in the Beta version of Anaplan, we’ve noticed that the Export button is unavailable when switching to the Beta environment. This limits our ability to export required data directly from modules. When the Export button is available, it works as expected — allowing us to export necessary data such as items used…
