--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Deployment # Delegated development and deployment {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## 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 full answer 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 {#c_DelegatedDevelopment__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. {#c_DelegatedDevelopment__table_ugl_svv_jdb__entry__3} | Assignment Method | Applies to | Available options | |-|-|-| | Setting deployment permissions in Manage Developers. See [Delegate development and deployment permissions to personnel](https://servicenow-prod.fluidtopics.net/XqrBTW_5C_i5oxndrgOX_g "A system administrator can assign a non-administrator user or group as a developer or deployment resource for a specific application. You can set permissions that designate what specific actions the assigned user can perform in the current instance, or make the user a Delegated Admin to grant access to all permissions at once.") | 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](https://servicenow-prod.fluidtopics.net/q2jD9c~nQ806nL~SkGQZFw "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."). | 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. | [ ] {#c_DelegatedDevelopment__table_ugl_svv_jdb} ## Application-specific permissions {#c_DelegatedDevelopment__section_av5_5lm_3db} Developer and deployment 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. Administrators must set developer (and optionally deployment) permissions for each 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. Important: If [Application administration](https://servicenow-prod.fluidtopics.net/Uydba_1DGlBpZYo3iIjnHw "Protect sensitive application data by using application administration to restrict how users acquire application-specific roles.") is enabled, only an application administrator for the target application can delegate developers for an application. Application administrators do not have system admin privileges. 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. 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 {#c_DelegatedDevelopment__section_n3z_vlm_3db} 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](https://servicenow-prod.fluidtopics.net/XqrBTW_5C_i5oxndrgOX_g "A system administrator can assign a non-administrator user or group as a developer or deployment resource for a specific application. You can set permissions that designate what specific actions the assigned user can perform in the current instance, or make the user a Delegated Admin to grant access to all permissions at once."). . **Related concepts** * [Application files](https://servicenow-prod.fluidtopics.net/2Ym~yBgZf8abZEGaAMrHBA "Application files are configuration records that allow developers to extend application functionality.") * [Application sharing](https://servicenow-prod.fluidtopics.net/0qsUoyNWaw2AguSTWFtfdg "Administrators can share applications that are complete and are ready for use on other instances.") **Related topics** * [Install a ServiceNow Store application](https://www.servicenow.com/docs/access?context=t_InstallApplications&version=australia&pubname=australia-platform-administration&ft:locale=en-US) * [Install an update to a ServiceNow Store application](https://www.servicenow.com/docs/access?context=t_InstallUpdates&version=australia&pubname=australia-platform-administration&ft:locale=en-US)