---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Update sets

# Update sets in ServiceNow Studio {#ariaid-title1}

* Release version: Australia
* 
* Updated May 21, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Use update sets in ServiceNow Studio to group configuration changes and move them as a unit to other instances for testing or deployment.

Update sets track configuration changes made in ServiceNow Studio so that admins and delegated developers can move those changes to other instances as a single deployable unit. Access update sets from within an individual application or from the
Deployment tab. Update set interactions in ServiceNow Studio follow the same patterns as on the ServiceNow AI Platform. For more information about tasks you can accomplish with update sets, see [System update sets](https://www.servicenow.com/docs/tY0pUBdQL8rXBWDe_awKqg "An update set is a group of configuration changes that can be moved from one instance to another. This feature allows administrators to group a series of changes into a named set and then move them as a unit to other systems for testing or deployment.").  
Administrators can perform the following actions with update sets to control the full deployment lifecycle.

* Create an update set to store local changes.
* Select the current update set to direct where new local changes are recorded.
* Commit an update set to prepare it for distribution.
* Report on the contents of update sets.
* Compare update sets to determine what differences they contain.
* Merge separate update sets into a single update set.
* Create an external file from an update set.
* Retrieve update sets from remote instances to pull in changes made on other instances.
* Apply retrieved update sets to install those changes on the current instance.
* Back out changes applied from an update set.
* Set system properties related to update sets to configure default update set behavior.
* Promote update sets for deployment via ReleaseOps. For more information, see [ReleaseOps](https://www.servicenow.com/docs/OGg~z86Jvh8RrLkeCibsBA "ReleaseOps automates deployment of changes across your pipeline, increases predictability and reliability of deployments, and reduces the risk of releasing changes to production.").
{#working-with-update-sets-in-servicenow-studio__ul_sjh_5pf_5cc}  
Delegated developers can perform the following actions with update sets in ServiceNow Studio to manage changes within their assigned applications.

* Create an update set to store local changes.
* Switch between update sets using the update set picker.
* Package changes for deployment using the Publish button in any app.  
  Note:  
  If your app was created in ServiceNow IDE and converted to Fluent, you must switch from ServiceNow Studio back into the ServiceNow IDE for the publishing and deployment process.
{#working-with-update-sets-in-servicenow-studio__ul_dzm_n5f_5cc}
* **[Create an update set in ServiceNow Studio](https://www.servicenow.com/docs/ODVF3TPQ9LhFcvAb4n36aA)**   
  Create an update set in ServiceNow Studio to package app changes for deployment to other instances.
* **[Mark an update set complete in ServiceNow Studio](https://www.servicenow.com/docs/sGOZCx2WMPzxP6dR4azdEA)**   
  Mark an update set as Complete in ServiceNow Studio to make the changes available for retrieval by other instances.