Why is Source Control read only for delegated developers?

[Craig22]

I've assigned the Source Control permission (via Manage Collaborators) to a scoped app for my delegated developers and they get the Source Control link show up but can't interact with it in any way.

Is there something else I need to do to enable them to do stuff with Source Control?

[JC15]

Granting the user the source_control role directly does not work. I also do not believe it is intended to be how users in App Engine Studio are given roles, based on my prior discussions with the ServiceNow team. 

Roles in app engine studio are assigned via:

1. Going into App Engine | Colloboration | Descriptors 
2. Clicking on Owner
3. Adding source_control role to Development Permission Sets tab related list. 

The problem, I believe is one of the Washington updates broke it, so that permission no longer works. It had worked over a year for us prior. It is also still broken in Xanadu based on testing in personal dev. 

https://docs.servicenow.com/bundle/xanadu-application-development/page/build/creator-studio/concept/...

[WORKFLOW-COWBOY]

Hi @JC15 - yes, the correct way long-term would be to add the "Development Permission Set" [sys_development_permission_set] named "Source Control" to an App Collaboration Descriptor for users that you intended to have that capability. 

I have tried that out and I see the same behavior that you're describing. 

[WORKFLOW-COWBOY]

The AES User can still see the Source Control window in the old green Studio, but can't see the Credentials field on the setup form. 

I'm thinking this issue overall may have something to do with the AES User's ability to read Credentials. I also think someone with 'admin' role has to set up the GitHub Credential for the AES User to use in Source Control.  

[JC15]

Thanks. Yes, we've had this setup and working for over a year before the update broke it, so I am familiar with the github setup process. I think this is a bug, especially because Submit is being impacted by source_control role. The credentials have already been setup by an admin (me). 

[JC15]

I think you are onto something. Giving them credential_admin (to access the cred) appeared to make both options become available. This is still a bug though, as you clearly wouldn't want to have to give users credential admin. Is there anyway to only share 1 credential (I dont know of any way). And like I said before, this repo had already been linked + setup by admin. 

In fact, walked through setting up test repo on personal dev and same results (didn't show up for creator user)