Delegated developer access and source control
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-18-2026 07:30 AM
Hi all,
Can anybody point me in the right direction for which role is needed for the delegated developer in ServiceNow Studio to get access to source control create branch, switch branch etc.
As admin I can easily do the same:
If my answer has helped with your question, please mark my answer as the accepted solution and give a thumbs up.
Best regards
Anders
Rising star 2024
MVP 2025
linkedIn: https://www.linkedin.com/in/andersskovbjerg/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hey there,
I just randomly stumbled across this from the ServiceNow SNUG Denmark group, but to answer your question:
The standard approach is to go to your application and select Manage developers / Collaborators (assuming you have an App Engine license). From there, you add the user and assign them custom permissions under "Application management." You can also create a few sys properties to reveal hidden fields like "Manage update set/"Source Control", or "Publish to update set".
However, speaking from experience, the built-in manage collaborators/developers feature can be a bit glitchy.
Here is a much more reliable workaround:
Go to your filter navigator (descriptor) and pull up the user you are trying to grant access to.
Edit their Development Permission Sets on the record.
Manually add the "Manage update set", "Source Control", or "Publish to update set" permission sets.
- Dont add both Manage update set & Publish to update set since for some reason they cancel each other out. Only add Manage Update set if so.
This method works for us like a charm!
Hope this helps.