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
To maintain efficiency and performance, model builders must periodically remove unused or irrelevant line items. At present, the [Referenced By] column in the blueprint provides visibility into dependencies between line items. However, for line items that are not referenced by other calculations, builders must manually…
When we use "Anaplan Extensions", we can check "Filters used in Pages" now. But we cannot check "Filters used in Saved Views" and "Filters used in Context Selector". We want to have a function that allows us to check "Filters used in Saved Views" and "Filters used in Context Selector" in "Anaplan Extensions".
When we access a model that belongs to a different Tenant that the one we are currently viewing, the Tenant does not switch automatically. Example: Tenant A: Model 1 Tenant B: Model 2 ① We view Model 1 (Tenant A) ② We try to access Model 2 (Tenant B) ⇒ Tenant does not switch automatically
