---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Instance-specific deployment user roles

# Instance-specific deployment user roles {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

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.
To learn more about managing per-user subscriptions, see [Managing per-user subscriptions in Subscription Management](https://www.servicenow.com/docs/access?context=managing-user-subscriptions-v2&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US) and contact your account representative.