Skip to main content
Solved

Restrict access to Aurena navigator

  • April 13, 2021
  • 1 reply
  • 241 views

Forum|alt.badge.img+3

Hi Community,

 

I need to restrict access to the different nodes in the Aurena navigator.

For example, only managers should see the Manager services node in the Human Capital Management.

What I noted is that all sub menus under Human Capital management is connected to the client PersonNavigator. When the projection PersonNavigator is granted to the user, all the nodes connected to it are shown regardless user has access.

How can we hide the navigator items users are not suppose to see?

 

Regards,

Krish

Best answer by Navinth Bakmeedeniya

It is correct that when a projection is granted to a user, he/she can see all pages related to that projection in the navigator. So the best architecture is to break the projections as appropriate while creating & create page groups based on each of them; so that different user communities could be granted (of course via permission sets) as needed.
 

But for the pages now you have, you can hide these node from users using navigator designer.

You can create a separate configuration context for this purpose, hide the required nodes there & set the configuration context to those users; so that the nodes would be hidden for them.

https://docs.ifs.com/techdocs/foundation1/045_administration_aurena/220_Configuration/330_configuration_contexts/default.htm

 

View original
Did this topic help you find an answer to your question?
This topic has been closed for comments

Navinth Bakmeedeniya
Hero (Employee)
Forum|alt.badge.img+14

It is correct that when a projection is granted to a user, he/she can see all pages related to that projection in the navigator. So the best architecture is to break the projections as appropriate while creating & create page groups based on each of them; so that different user communities could be granted (of course via permission sets) as needed.
 

But for the pages now you have, you can hide these node from users using navigator designer.

You can create a separate configuration context for this purpose, hide the required nodes there & set the configuration context to those users; so that the nodes would be hidden for them.

https://docs.ifs.com/techdocs/foundation1/045_administration_aurena/220_Configuration/330_configuration_contexts/default.htm

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings