Delegated development and deployment
Summarize
Summary of Delegated Development and Deployment
Delegated development and deployment in ServiceNow allows non-admin users to develop and deploy applications on the AI Platform. This is particularly useful for organizations looking to empower designated developers while maintaining system control.
Show less
Key Features
- Application-Specific Admin Role: Administrators can delegate application development to users with application-specific admin roles.
- Deployment Task Delegation: Deployment tasks such as application publishing and updates can be assigned to developers or non-admins, including Change Management personnel.
- Permission Management: Deployment permissions can be set for specific applications and users, allowing for granular control over who can publish or upgrade applications.
- Instance-Level Role Assignment: Local non-production instances allow for first-time installations and upgrades for applications associated with the same company.
- Application-Specific Permissions: Developer and deployment permissions are tailored to each application, ensuring that access is appropriately restricted.
Key Outcomes
By utilizing delegated development and deployment, system admins can:
- Empower designated developers without granting full system admin privileges.
- Maintain control over the application development process while distributing tasks effectively.
- Ensure the correct permissions are set, enabling developers to perform necessary functions without compromising system integrity.
Delegated developers must also hold the application administrator role to execute their permissions effectively. This setup preserves the system admin's control while fostering a collaborative development environment.
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.
.