ACL on Task.Universal Request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Good morning,
I have created a record producer and have added Task.Universal Request to the related links.
As an admin I can access the interceptor page but as a non-admin I cannot.
What ACL needs to be updated for this?
I would have thought task.universal request but that did not work (OOB there is a write ACL, I also created a read and create).
Any help is always appreciated,
Rachel
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @rconstantino ,
Do not update the Task.Universal Request ACL for this. That ACL controls access to the Universal Request reference field on Task; it does not control whether the user can open the Task -> Universal Request interceptor.
The OOB Task -> Universal Request related list uses an interceptor when the user clicks New.
Recommended fix:
1. Assign the user the Universal Request routing agent role:
sn_uni_req.routing_agent
Prefer assigning the role through the appropriate routing group instead of directly to the user.
2. Make sure the user also has create access to the target task type that the interceptor should create.
For example:
Incident -> user needs the required ITSM/ITIL access.
HR Case -> user needs the appropriate HR role.
Custom task table -> user needs the create ACL/role for that table.
3. If you created a custom task table/record producer, also verify that the table is registered under:
Universal Request > Administration > Service Configuration
4. Impersonate the affected user and enable:
System Security > Debug Security Rules
Then click New from the Task -> Universal Request related list. This will show exactly which ACL is denying access.
I would not modify the OOB ACLs unless the security debugger confirms that a specific ACL is the actual blocker.
The most likely issue is that the non-admin user does not have the required Universal Request routing role and/or create permission on the target task table.
Hope this helps!
If this response helped, please mark it as Helpful.
If it resolves your issue, please Accept it as Solution.
Kind Regards,
Abhishek Pal
