Non-Admin users are unable to commit update sets
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2023 03:55 PM
I made changes as per ServiceNow KB Article and community article to grant retrieve/preview/commit access to non-admin role users. Non-Admins are able to retrieve/preview but are unable to commit the update sets even though 'Commit Update Set' UI Action is visible to them post retrieval. Below is the error message that is showing up when trying to commit even though the update set and update are in global scope.
Wanted to know if there is a way to fix this issue.
Thank you!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-14-2023 07:00 PM
Hi @Prashanth ,
Does the user who is committing the update set have access to all the updates that are captured in it.
I mean, if you have modified something in the structure of a table, and the user who is committing should also have access to that particular area.
Anvesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 08:14 AM
Hi Anvesh,
Yes, the user captured the updates and the user trying to commit the update set are the same in our case.
Thanks,
Prashanth

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2023 05:20 AM
@Prashanth Please go through this community post https://www.servicenow.com/community/itsm-forum/roles-for-update-sets/m-p/583792 and see if you can assign similar roles to the non admin users so that they can commit the changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-17-2023 08:59 AM
Hi Sandeep,
I created and assigned the roles to the non-admin users as mentioned in the article you shared and also created and modified ACLs mentioned to give them access to update set tables.
Thanks,
Prashanth