Delegated development and deployment
Summarize
Summary of Delegated Development and Deployment
Delegated development and deployment in ServiceNow enables designated users, without a system admin role, to develop or deploy applications. This feature allows for streamlined application management by granting application-specific admin roles to selected developers, enhancing collaboration and efficiency within teams.
Show less
Key Features
- Delegated Development: Designated developers can create applications if granted the application-specific admin role.
- Delegated Deployment: Deployment tasks, including application publishing and updates, can be assigned to developers or non-admin users, such as Change Management personnel.
- Application-Specific Permissions: Developer and deployment permissions are tailored for each application, ensuring that users have access only to the necessary files and functions.
- Control Retention: System admins maintain overall control while granting specific permissions, eliminating the need to elevate developers to system admin status.
Key Outcomes
By leveraging delegated development and deployment, organizations can enhance productivity through efficient task delegation. Administrators can configure permissions at both the application and instance levels, ensuring that developers can focus on their roles while system admins oversee system integrity. This results in a more agile development process, reducing bottlenecks and improving application lifecycle management.
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.
.