Setting up Granular Delegation
Set up Granular Delegation so your employees can delegate their tasks to other employees.
Configuration steps
- Activate Granular Delegation
- Define what tasks can be delegated by adding the table that holds the tasks: Add delegation rule tables
- For each delegation table: Create delegation rules
- Define the users that can delegate tasks and to whom they can be delegated: Create a delegate
Installed with Granular Delegation
Activate the Granular Delegation plugin (com.glide.granular_service_delegation) for the ServiceNow AI Platform if you have the admin role. For more information, see Activate Granular Delegation.
Granular delegation has separate records for specifying a delegate and specifying what content the delegate can access. You create a Delegate record each time you want to delegate your service tasks to another user.
Administrators create delegation rules to allow the delegation of specific records. Access Control Rules (ACLs) determine if a delegate can access the records that match the delegation rules assigned to them. Creating delegation rules requires an administrator to be familiar with the data model of the delegated services.
| Role | Description | Contains roles |
|---|---|---|
| Delegation admin [delegation_admin] | Manages granular delegation, setting up delegation rules. | N/A |
- User Criteria (user_criteria)
- Granular delegation can use the User Criteria (user_criteria) table to determine who can be a delegate or a delegator. For more information, see Create delegation rules.
- System properties
- The com.glide.delegation.default_days_since_update system property determines how many days to retain inactive delegation records for users or delegates. The default is seven (7) days and can be changed to a maximum of 30 days.
- Scheduled jobs
- The Clean Granular Delegation Records scheduled job runs daily and deletes inactive delegation records based on the com.glide.delegation.default_days_since_update system property value.