Delegated development and deployment
Summarize
Summary of Delegated Development and Deployment
Delegated development enables selected users, who do not hold a system admin role, to create or deploy applications on the ServiceNow AI Platform. Users with application-specific or system-level admin roles can delegate these tasks to designated developers at the application level.
Show less
Key Features
- Delegated Development: Allows designated developers to create applications based on specific permissions set by administrators.
- Delegated Deployment: Users can delegate deployment tasks such as application publishing and installations to non-admin users, including Change Management personnel.
- Application-Specific Permissions: Developer and deployment permissions are tailored for each application, ensuring that access is controlled and appropriate to each developer's role.
- Role Assignment: Permissions can be set at both the application and instance level, ensuring that users can only install applications relevant to their specific company instance.
Key Outcomes
By utilizing delegated development and deployment, system administrators can maintain control without needing to elevate developers to system admin status. This streamlined approach allows for more efficient application management while ensuring that developers have the necessary permissions to perform their tasks effectively. Administrators must be familiar with the application files and system structure to set these permissions accurately, thus enhancing overall application governance.
Delegated development allows designated users without a system admin role to develop or deploy applications on the ServiceNow AI Platform.
If you have the application-specific admin role or the system-level admin role, you can delegate application development to designated developers at the application level.
Delegated deployment tasks
You can also delegate deployment tasks (application publishing, first-time installation, or update) to developers or non-admin users, such as Change Management personnel. You delegate deployment tasks to specific users at the application level, or through assignment of specific user roles at the instance level.
| Assignment Method | Applies to | Available options |
|---|---|---|
| Setting deployment permissions in Manage Developers. See Delegate development and deployment permissions to personnel | Specific applications | Publishing and upgrades of specific applications. Publishing options include the application repository, ServiceNow Store, and update sets. |
| Assignment of deployment user roles to specific persons. See Instance-specific deployment user roles. | Local non-production instance (for example, Development or QA) | First-time installations and upgrades of all applications that contain the same company as the current instance. 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. |
Application-specific permissions
Setting each permission grants one or more system-managed delegated development roles, allowing system admins to retain control over the system. System admins no longer have to elevate developers (or users who deploy applications) to the system admin role to enable them to develop or deploy applications.
Developer and deployment permissions example
As a system administrator, you want to assign Abel Tuter certain developer and deployment permissions for a specific application in your development instance. For more details on developer and deployment permissions, see Delegate development and deployment permissions to personnel.