Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store

Delegated development

Log in to subscribe to topics and get notified when content changes.

Delegated development

Delegated development allows users without the system admin role to develop applications on the ServiceNow platform.

Application administrators or system admins can manage designated developers by specifying which users and groups have access to application content.
  • If Application administration is enabled, only an application administrator for the target application can delegate developers to an application. Application administrators do not have system admin privileges.
  • If application administration is not enabled, a system admin can delegate developers.
Figure 1. Sample developer permissions
For each application, application administrators can:
  • Grant non-system admin users the ability to develop 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 or group as a developer.
Important: To enable a delegated developer to perform the functions granted in the developer permissions, the delegated developer must also be given the application administrator role.

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

Although system admins can still manually assign and remove roles, they are encouraged to let the system 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. Application administrators must set developer permissions for each application.

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.