Hi all,
We are looking at the "Profiles" functionality as a means to control the UI visibility.
I was reading through the documentation that the context specific "Configure Actions for Roles" will over ride the Org wide profile settings.
The documentation reference is below.
Default Visibility for Application Context Managers
The site and organization administrator can choose to set defaults for and hide control over a specific product, library, project, or other application context action or user interface element. That is, the site and organization administrator can carefully control which elements that application context managers (project, product, and library managers) are able to override in a context instance.
Removing the ability for an application context manager to override a profile setting is done by globally hiding visibility to the Configure Actions for Roles action for a specific context. If this is done, then the visibility of actions and areas of the user interface in a context instance cannot be modified by that application context manager.
It seems that on already created contexts, applying the profile settings seems to be a challenge.
All I want to know is that a simple way to disable the Context setting for the UI for Roles, so that my profile setting at Org level is activated.
Is there preference or property to achieve this?
Any good practices on profiles? Dos and Donts?
Best Regards
Hari