--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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 --- # Source control integration # Source control integration in ServiceNow Studio {#ariaid-title1} Release version: Australia Updated May 7, 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 Source control integration in ServiceNow Studio ServiceNow Studio allows you to link scoped or global applications on non-production instances to Git source control repositories. This integration manages application metadata changes, enabling developers to save, manage, and share multiple application versions efficiently. It supports importing applications from Git, pulling remote changes, committing local changes, and managing branches and tags for version control. Show full answer Show less ## Integration Requirements * You must have the **admin** role to link applications to source control. * The non-production instance must have network access to the Git repository. * Each application must reside in its own Git repository with read/write access credentials. * Credentials for the repository are shared by all developers on the instance. ## Key Features in ServiceNow Studio * Edit repository credentials directly within Studio. * Commit all local changes to the Git repository. * Apply changes pulled from the remote repository. * Create, switch, and manage multiple branches. * Import applications from remote Git repositories. Note: Source control integration is not supported on production instances. For production, use the application repository, update sets, or ServiceNow Studio application sharing features. ## Working with Git Repositories Outside ServiceNow Studio The ServiceNow AI Platform offers limited capabilities to modify linked application files directly in Git repositories. Developers can move files to different directory structures by configuring the **path** parameter in the `snsourcecontrol.properties` file. The system uses a `checksum.txt` file to detect external changes and triggers validation and sanitization processes as needed. * Sanitization removes unsupported files/folders and aborts operations on critical XML schema validation failures. * Only files within the defined application path in `snsourcecontrol.properties` are managed; other repository content is ignored. ## Connecting Through a MID Server To access Git repositories behind firewalls, you can use an existing MID Server to securely connect ServiceNow Studio to the source control repository. ## Security and Permissions Role permissions govern access to source control features. For managing collaborators and roles, refer to the Application Collaboration documentation. ## Additional Capabilities * **Metadata source control:** Manage application versions, commit changes, and collaborate with other developers through Git repositories. * **Fluent source control:** Connect to remote Git repositories to track and manage Fluent applications within ServiceNow Studio. Link your application to a Git source control repository in ServiceNow Studio to save, manage, and share multiple versions of a global or scoped application from a non-production instance. ## Metadata source control {#source-control-integration__section_xyr_n5y_xjc} Metadata source control processes changes in the metadata of your application. Linking an application to source control enables all application developers on a non-production instance to: * Import applications from a Git repository. * Pull and apply remote changes from a Git repository. * Commit all local changes on the instance to a Git repository. * Create tags to permanently link to a specific version of an application. * Create branches to maintain multiple versions of an application at the same time. {#source-control-integration__ul_f23_qsk_p5} ## What are the integration requirements? {#source-control-integration__section_bgq_czg_kjb} To link an application to source control: * You must have the admin role. * The non-production instance must have network access to the Git repository. * Each application must be in its own Git repository. * The repository user credentials must grant read and write access. {#source-control-integration__ul_spw_bhl_p5} Note: All application developers on the instance share a single set of credentials per repository. ## What can you do with source control in ServiceNow Studio? {#source-control-integration__section_k2d_kyg_kjb} After linking an application to source control, you can use ServiceNow Studio to manage the repository. From ServiceNow Studio, you can: * Edit the application repository credentials. * Commit all local changes on the instance. * Apply remote changes from the repository. * Create a branch. * Switch branches. * Import an application from a remote repository. {#source-control-integration__ul_u55_hl4_q5} Source control integration does not support managing applications on a production instance. To manage applications on a production instance, use the application repository, an update set, or ServiceNow Studio. For more information, see [Application sharing](https://www.servicenow.com/docs/0qsUoyNWaw2AguSTWFtfdg "Administrators can share applications that are complete and are ready for use on other instances."). ## What can you do with source control from a Git repository? {#source-control-integration__section_spn_nyg_kjb} The ServiceNow AI Platform offers limited support for modifying linked application files outside of an instance. From Git, developers can: * Move application files to a different Git directory structure. * Edit application files outside of ServiceNow Studio. {#source-control-integration__ul_gtn_34f_kjb} The system generates a properties text file called sn_source_control.properties at the root level of the repository. To move application files to a different Git directory structure, set the path parameter to specify the subfolder path containing the application files. For example, to move your application to the src/app subfolder, set the path to `path=src/app`. The system generates a checksum.txt file in the Git repository to determine if any application files have been changed outside of ServiceNow Studio. When the checksum value from the file matches the current checksum value, the integration skips the validation and sanitization process. When the checksum values do not match, the integration validates and sanitizes the application files as part of the source control operation. The sanitization process: * Creates upgrade log entries for each sanitization action taken. * Removes unsupported folders and files from the repository. * Aborts all source control operations when a system application file fails XML schema validation. For example, if a database dictionary record fails XML schema validation, the system aborts all operations. * Skips the current source control operation when a non-system application file fails XML schema validation. {#source-control-integration__ul_sqt_z4f_kjb} The Git integration sanitizes only content within the application path listed in the sn_source_control.properties file. Repository content outside the application path is ignored. ## How do I connect through a MID Server? {#source-control-integration__section_ew2_4y1_njb} Use an existing MID Server to connect to a source control repository. Connecting an application through a MID Server enables access to repositories behind a firewall. ## Source control role permissions {#source-control-integration__section_adt_l4c_yxb} For more information about roles and collaborators, see [Application collaboration](https://www.servicenow.com/docs/l0iGsbq1p9eq24jLSyx4og "People with admin privileges can manage the permissions of developers collaborating on an application."). * **[Metadata source control in ServiceNow Studio](https://www.servicenow.com/docs/C6VXFNDLM_lYwVKkGwOo5Q)** Use metadata source control in ServiceNow Studio to manage app versions, commit changes, and collaborate with other developers through a linked Git repository. * **[Fluent source control in ServiceNow Studio](https://www.servicenow.com/docs/olSzCoafs_2yv2IK6vEnxA)** Connect to remote Git repositories to track and manage Fluent applications in ServiceNow Studio.