Hi @Aaron Duncan
To allow a user to see all fields without giving them the broad privileges associated with the admin role, you need to identify which specific roles or ACLs control access to these fields and then grant an appropriate role to the users.
Steps
1. Identify Required Roles or ACLs:
- ACLs: Check the Access Control List rules that are applied to the Engagement Template table or the specific fields within this table. Look for any ACLs that require the admin role or another specific role for read access. You can search for ACLs in the Application Navigator by typing “Access Control (ACL)”.
- Roles: Some fields might be associated with specific roles outside of ACLs, especially if custom development is involved. If documentation is available, review it to see if certain roles are required to access Engagement Templates fully.
2. Create or Modify Roles:
If no existing role besides admin gives the appropriate access:
- Consider creating a new role that specifically grants access to the parts of Engagement Templates that users need. Then, assign this role to the appropriate users.
- To avoid granting excessive permissions, be precise about which rights and access levels are included in this role.
3. Update ACLs:
If specific fields are not visible because of restrictive ACLs:
- Modify the existing ACLs to include the new role you’ve created or another existing role that’s suitable for users who need to create Engagement Templates. Ensure these ACLs grant at least “read” access, or more if users need to modify or create templates.
Note: Please Mark this Helpful and Accepted Solution. If this Helps you to understand. This will help both the community and me..
- Keep Learning
Thanks & Regards
Deepak Sharma
