Creating a Permission Group
You can see the newly created permission group in the list view.
The application automatically adds the View All permission to the AppRegistry object, allowing non-administrative users to view the Conga Advantage Platform administration apps. You can change the object permission if necessary.
Assigning Object Permissions
To delete an object permission, select it from the list and click the Delete Object Permissions button.
Assigning Field Permissions
Assigning Record-Type Permissions
Adding Scope Permissions
Global, user, and account scopes only apply to an object if ViewAll or ModifyAll is not set up. Only queryable fields are used to set read criteria for all global and user scopes.
Adding Property Scope Permissions
- You have administrator access to manage roles and permission groups.
- The required Property Objects already exist and are active.
- The business objects you want to control include lookup fields that reference the Property Object.
- The Permission Group is created or identified for update.
Property Scope permissions allow you to control record-level access using Property-Based Access Control (PBAC). With PBAC, you grant or restrict access based on business properties, such as classification, region, or contract group, rather than creating multiple roles.
You configure Property Scope permissions inside a Permission Group. Once assigned to a role, these permissions determine which records users can create, view, update, or delete based on the property values linked to those records.
For more information, see Property-Based Access Control (PBAC).
- Assign the updated role to users who need property-based access.
- Review existing Permission Groups to reduce role complexity using PBAC.
- Test access with sample users to confirm that property values are enforced correctly.
