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

Instance-specific deployment user roles

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

Instance-specific deployment user roles

Assign roles that enable non-admin users install or upgrade all applications in specific instances. You delegate these tasks by manually assigning specific user roles per instance.

For example, you can assign user roles to Change Management personnel that allow them to perform application installations in non-production (development or QA) instances.

Important: Give careful thought to whom, and in what instances you assign installation and upgrade user roles. You may only want to assign these roles to non-system administrators in non-production instances (for example, Developer or QA), but decline to do so in production instances. Given the potential impact of installing and upgrading applications, you may want to leave the responsibility for installations and upgrades in production instances to a system administrator.

Add deployment user roles

A system administrator can assign user roles to specific personnel that allow them to perform first application installations only, or install and upgrade applications in a local instance.

Before you begin

Role required: admin

Procedure

  1. Navigate to User Administration > Users and then open a user record.
    Note: For details on how to assign a role to a user, refer to Assign a user role .
  2. In the Roles related list, click Edit.
  3. In the Collection list, select the desired deployment roles, and then click Add.
    Table 1. Delegated deployment roles
    User Role Description
    sn_appclient.app_client_company_installer Allows a designated person to perform first-time installations of applications displayed on the Application Client page that contain the same company as the current instance. A user with this role cannot install an application for another company.

    For example, applications for ABC Company and XYZ Company display on the Application Client page. A user with this role can only install XYZ Company applications when logged in to a XYZ Company instance. The user cannot install applications for ABC Company.

    Note: While this role does not grant a user the ability to upgrade applications, the system auto-adds a delegated developer upgrade role after the user does a first-time installation. The user can then perform upgrades for the application in the local instance. For more details, see System-managed developer and deployment roles.
    sn_appclient.app_client_user Allows a designated person to install and upgrade all applications displayed on the Application Client page.
  4. Click Save.

System-managed developer and deployment roles

Although system admins can still manually assign and remove the user roles, they are encouraged to let the system manage the following delegated developer roles.

Role Description
delegated_developer User has one or more developer permissions.
Roles that start with an sn_dd prefix (for example, sn_dd_<app_name>_upgrade_app) User has an application-specific developer permission. The role name indicates the application scope to which it applies.

For example, after a user with a sn_appclient.app_client_company_installer role installs a company application, the system automatically grants a sn_dd_<app_name>_upgrade_app delegated deployment role. This role allows the user to upgrade the application when future updates are published to the Application Client page.

Note: Users with delegated developer roles cannot add or remove the system admin role.
Feedback