Delegated developer access and source control

[AndersBGS]

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:

[NotNowBoss]

Hey @AndersBGS 

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:

1. Go to your filter navigator (descriptor) and pull up the user you are trying to grant access to.

2. Edit their Development Permission Sets on the record.

3. Manually add the "Manage update set", "Source Control", or "Publish to update set" permission sets.

   1. 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.



Update: There is a known issue where having App Engine installed causes the "Manage update set" and "Publish to update set" properties to be hidden if "Manage Collaborators" is visible.
ServiceNow has acknowledged this and logged Problem Record PRB1912330. A fix is currently targeted for the Brasil release

[Benjamin JS]

You need to give the user the credential_admin role

[AndersBGS]

Hi @Benjamin JS 

Why would I provide a delegated developer an admin role? That shouldn't be necessary. 

[Benjamin JS]

I second that, I found out due to the new ServiceNow IDE plugin broke our SN scopes repo links, although it still had the sys_repo_config record intact, the source control button was nowhere to be seen. Workaround from ServiceNow was making a user we gave only delegated_developer role to, problem was they forgot to mention that you need credential_admin for the source control button to be available for interaction.