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
Business Problem & Current Limitation Current State: In our current Polaris implementation, the cumulative dimension index across just five core business dimensions has reached 55. The Constraint: With a hard ceiling at 64, this leaves a headroom of only 9 remaining indexes across the entire workspace/model scope. Direct…
Dear all, Some times your system refuses us to log in. It seems it is because the password is no longer valid and has to be renewed. However absolutely no information is given to the user. Therefore he/she tries to connect again and again, until he/she thinks "oh, that should be the password that has expired". This is…
I've come across this need more than once now so I figured I'd post it here for the Anaplan product team! We have a client who utilizes a primary hierarchy for a core list but developed the need to see the lowest level in that primary hierarchy rolling up to an alternate hierarchy of parent list members. In their Polaris…
