Did You Know? Dynamically hide page components using Page Composer
Access to pages and page components (e.g. tabs, buttons, actions) is primarily governed by application roles and their constituent privileges. However, what do you do when a requirement exists to hide a page component for a subset of users, but the securing privilege only applies at the page level?
The documents attached to this post explore two techniques that can be used to dynamically hide page components using Page Composer:-
- Dynamically hide page components based on a profile option value.
- Dynamically hide page components using custom duty roles.