A delegated developer in ServiceNow is a designated user who does not hold the system admin role but still builds and deploys a particular application. Access is set per application through developer and deployment permissions, which an admin assigns in Manage Developers. A single Delegated Admin permission bundles all of the delegated development permissions into one grant.
What delegated development lets non-admin users do
Delegated development lets designated users without the system admin role develop or deploy applications on the ServiceNow AI Platform. The idea is to widen who can build apps without widening who can administer the whole instance. A user who holds the application-specific admin role or the system-level admin role can delegate development to designated developers at the application level.
System admins no longer have to elevate developers to the system admin role, so they keep control of the instance while developers work on individual applications. Developers and deployers do not need the system admin role in order to build or deploy an app.
Deployment work can also go to someone outside the admin group. A non-administrator user or group can be assigned as a developer or deployment resource for a specific application. Deployment tasks such as publishing, first-time installation or an update can go to developers, or to non-admin users such as Change Management personnel.
Roles involved in delegating development
Delegation involves these roles and one permission:
| Role | What it does in delegation |
|---|---|
| System Admin | Delegates development to designated developers on an application |
| Delegated Admin (permission) | Grants every delegated development permission on one application in a single grant |
| Application Administrator | Delegates developers to the application it administers, when Application administration is enabled |
| Delegated Developer | Develops applications on the platform |
| sn_dd_<app_name>_upgrade_app | System-managed deployment role for one application. Lets the holder upgrade that application when future updates are published |
When Application administration is enabled, the application administrator for the target application is the person who can delegate developers to that application. If the setting is not enabled, an admin user can delegate developers. Application administrators do not have system admin privileges.
A delegated developer must also hold the application administrator role for the application to carry out the functions its developer permissions grant. This applies when Application administration is enabled. The developer permissions alone do not cover each function.
Permissions are scoped to one application at a time
Developer and deployment permissions are set on the record of each scoped application, through Manage Developers. Global applications do not take these permissions. A developer with access on one application has none on another, so an administrator sets developer permissions for each application separately, and may optionally set deployment permissions too.
Developer permissions an admin can grant
Administrators assign these permissions to a user or a group for a specific application through Manage Developers. In the Australia release line, the developer permissions are these.
| Permission | What it grants |
|---|---|
| Delete Application | Deletes a scoped application |
| Source Control | Full access to source control |
| All File Types | Access to all application file types configured in Manage Developers in Application Creator. Equivalent to granting the admin role, with some limitations |
| Playbooks | The Playbooks design environment. Editing activity subflows or actions also requires the Flow Designer permission |
| Integrations | Web service APIs, REST APIs, data sources and Integration Hub – Import |
| Reporting | Reports and scheduled reports |
| Notifications | Automatic email notifications |
| Decision Tables | Decision logic built from if-then rules |
| Mobile Builders | Mobile builders, such as Mobile App Builder |
| UI Builder | Creating pages for experiences |
| Workflow | The Workflow Editor and Activity Creator |
| Service Catalog | Catalog file types such as catalog items, record producers and variables |
| Service Portal | Service Portal editors and tools |
| Workflow Studio | The Workflow Studio design environment for flows and actions. Script action steps also require Allow Scripting |
| Tables & Forms | Model and layout file types such as table columns, form layouts and list layouts |
| Manage ACLs & Roles | Security file types such as access controls and user roles |
| Allow Scripting | Write access to script fields such as business rules, client scripts and Workflow Studio script action steps. Also adds the SNC scripting role |
| Delegated Admin | All delegated development permissions in one grant. Also adds the SNC scripting role |
Manage Collaborators and Invite Collaborators are not in the table above. They are available only with the Developer Collaborator feature and do not appear in Manage Developers. Manage Collaborators lets the developer invite and manage users and groups, including other developers. Invite Collaborators covers inviting users and groups, including other developers. When the App Collaboration component is installed, the Manage Developers link is labelled Manage collaborators.
What the Delegated Admin permission covers
The Delegated Admin permission grants all delegated development permissions at once, so an administrator does not have to add them one at a time.
Delegated Admin also adds the SNC scripting role, as the Allow Scripting permission does.
Deployment permissions and update set rules
Deployment permissions cover moving a finished application out of the development instance. The six options are:
| Permission | What it grants |
|---|---|
| Upgrade App | Upgrading the application after it is installed in the current instance |
| Publish To Update Set | Publishing the application to an update set in the current instance |
| Publish To App Store | Publishing the application to the ServiceNow Store from the current instance |
| Manage Update Set | Manages local and retrieved update sets |
| Publish To App Repo | Publishing the application to the application repository in the current instance |
| Submit for Deployment | Submitting the application for review and deployment |
Publish To Update Set is hidden by default, and it appears only after a system administrator enables it. Publish To Update Set and Manage Update Set cannot be held by the same user, so a user who can publish to an update set cannot also manage update sets, and the reverse.
Submit for Deployment depends on the Developer Collaborator feature and does not appear in the Manage Developers screen.
Manage Developers deployment permissions cover publishing and upgrades. The publishing targets are the application repository, the ServiceNow Store, or an update set.
Deployment access on specific instances is handled by instance-specific deployment user roles, which let non-admin users install or upgrade applications from the same company as that instance.
How the delegated developer role works inside ServiceNow Studio
ServiceNow Studio gives delegated developers a narrower scope than the admin role. The delegated_developer role limits access to the app or apps it has been delegated to. Within that scope, a delegated developer can open ServiceNow Studio, modify the delegated apps, package changes into update sets, create and update app files and metadata, and submit apps for deployment through update sets, pipelines or the Application Repository. Access can vary with how the instance is configured.
The legacy Guided Application Creator works differently at the moment of creation. ServiceNow Studio provides the current experience for the same work. A user who builds an app with it automatically receives the delegated_developer role for that new app, so the creator can keep working on it without a separate grant.
Metadata-specific admin roles offer a narrower option than a full delegated developer role. A script include admin can create, read, update and delete any script include on the platform and develop script includes in ServiceNow Studio. Each metadata-specific admin role has to enable create, read, update and delete access for its own metadata type inside Studio, and it can be placed in the experience switcher.
Frequently asked questions
Does a delegated developer need the system admin role?
No. Designated users without the system admin role can develop or deploy applications. When Application administration is enabled, they also need the application administrator role for the application to carry out the functions their developer permissions grant.
Does a permission granted on one application apply to another application?
No. Developer and deployment permissions are set for one application at a time, and access to one application gives no developer permissions on a different application.
Which permission lets a developer write business rules and client scripts?
Allow Scripting. It gives write access to script fields such as business rules and client scripts, and it adds the SNC scripting role.
How can one person receive all delegated development permissions at once?
Grant the Delegated Admin permission. It bundles all of the delegated development permissions into one grant, and it also adds the SNC scripting role.
Why do some deployment options not appear for a delegated developer?
Publish To Update Set is hidden until a system administrator enables it. Submit for Deployment depends on the Developer Collaborator feature and does not appear in Manage Developers.
Who can delegate developers for a given application?
A user with the application-specific admin role or the system-level admin role can delegate development. When Application administration is enabled, an application administrator for that application is the person who can delegate developers to it.