Delegated development

Delegated development allows non-administrators to develop applications on the ServiceNow platform.

Administrators can use Studio to manage development users and the application content they can access.
Figure 1. Sample developer permissions
For each application, administrators can:
  • Grant non-admin users the ability to develop scoped applications.
  • Specify which application file types the developer can access.
  • Grant the developer access to security records.
  • Grant the developer access to script fields.
  • Remove a user as a developer.

Each developer permission grants one or more delegated-development-specific roles. These roles allow administrators to retain control over the system since they no longer have to elevate developers to the admin role just to create applications.

While administrators can still manually assign and remove roles, they are encouraged to let Studio manage the following delegated developer roles.

Table 1. Delegated developer roles
Role Description
delegated_developer Indicates that the user has one or more developer permissions.
Roles that start with an sn_dd prefix Indicates that this user has an application-specific developer permission. The role name indicates the application scope to which it applies.
Note: Delegated development cannot add or remove the admin role.

Developer permissions are application-specific. For example, a developer who has permission to access all file types for one application does not necessarily have any developer permissions for another application. Administrators must set developer permissions for each application.

Administrators must be familiar with application files and the system table structure to set developer permissions. For example, a developer expected to create advanced business rules needs both the All File Types and Allow Scripting developer permissions.