Release Coordinators should be able to create releases

Go to solution
Kevin Tran
Tera Contributor

‎09-05-2025 12:49 AM - edited ‎09-05-2025 12:50 AM

Would it be possible to give the ability create releases to the sn_dpr_model.release_coordinator role?

 

So far, only the Release Admins and Product Managers can create releases.

 

Attempted to update the ACL for the release coordinator to create releases

but it's blocked by other UI builder pages and modals within the workspace after clicking "Create Release".

 

Please see if the product team can add this to enhancement patches.

0 Helpfuls
  • 1,446 Views
1 ACCEPTED SOLUTION

Go to solution
Bhanu29
ServiceNow Employee

‎09-05-2025 01:21 AM

Currently, Release Admins and Product Managers have the ability to create releases. If you want Release Coordinators to also have this access, you can assign the release_admin role as a sub-role of release_coordinator in the sys_user_role_contains table as a workaround. However, since we have created specific roles for specific functionalities, granting create release access to all roles deviates from the original role design purpose. The Release Coordinator’s primary responsibility is to coordinate release activities, not to administer or configure releases.

View solution in original post

0 Helpfuls
6 REPLIES 6

Go to solution
SuryakiranM4342
ServiceNow Employee
In response to johannarami

‎03-04-2026 06:31 PM - edited ‎03-04-2026 06:31 PM

Hi @johannarami ,

A Release Coordinator can perform release activities such as completing phases, adding tasks, key dates, CIs, and CRs.

Whereas a Release User has read-only access across all releases, products, and the release calendar.

0 Helpfuls

Go to solution
Marida LH
Tera Contributor
In response to Bhanu29

yesterday - last edited 19 hours ago

Hi Bhanu,

 

We are currently implementing DPR and as a Managed Services Provider this does not quite work. The reason for saying that, is:

  • Release Manager - this gives admin access which allows you to set up DPR, including linking to external tools. When setting up aspects such a templates, policies and calendars we want to drive a standard (compliance) across our various customers. This level of admin is something we only want one or two individuals to have.
  • Product Manager - again, because this directly affects the CSDM, it is something that has to go via a controlled process and also should be reflected in DEV, Test, Pre-PROD and PROD. Raising a Release where you are requesting a new product to be added, typically only happens in PROD (where it is customer related). The out-of-the-box setup creates a REQ and auto-approves it. Again, this lack governance in a MSP type instance.
  • Release Coordinator - in a MSP environment where we want the above to be in place, this role would work for day-to-day Release Manager, but now we are running into the issues that they cannot create a Release.

So what seems to be lacking, is a Release Admin type role (currently Release Manager) and then a role that enables a Release Manager to raise and manage a Release. This will enable the required governance for any standards we are managing.

0 Helpfuls