---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Legacy - Import application or application-customization from source control

# Legacy - Import application or application-customization from source control {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Import an application or application-customization from a source control repository
to continue developing it on this instance.

## Antes de Iniciar

Importante:  
Starting with the Xanadu release, the legacy version of ServiceNow Studio is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. For details on the deprecation process, see the [Deprecation Process \[KB0867184\]](https://support.servicenow.com/kb_view.do?sysparm_article=KB0867184) article in the Now Support Knowledge Base.

Try building and editing apps in the current version of ServiceNow Studio instead. For more information, see [ServiceNow Studio](https://servicenow-prod.fluidtopics.net/HJE5fDsb~bjmVZ9BqGtS8w "ServiceNow Studio provides a unified experience for all ServiceNow development activities, enabling admins and developers to extend base system solutions and create custom apps with ease. Use ServiceNow Studio to build apps and app files with integrated tools, access and edit app metadata in scoped and global apps, and package app changes for deployment, all in one powerful development tool.").

* Role required: admin or source_control
  * Restrict permissions on the access token to allow read and write access to the Git repository.
  * The repository user credentials must grant read and write access.

  {#t_ImportAppFromSourceControl__ul_s1f_byv_45b}For more information, see [Link an application or
  application-customization to source control](https://servicenow-prod.fluidtopics.net/2oVB7fYJ7Iq7VapMevRcow "Linking an application or application-customization to source control allows application developers to manage changes from a Git repository.").
* Verify that the non-production instance has network access to the Git repository.
* Verify that the repository contains a valid application.
* Ensure that users add the email address to their respective Users Table (ServiceNow sys_user) record that they use in their commits to the Git repository.
* Learn more about application-customizations [Managing
  application-customizations](https://servicenow-prod.fluidtopics.net/eC7fr6tvn0tDaU~EbtecVA "You can manage your company's customizations for applications that belong to other organizations or a scoped ServiceNow plug-in.").
{#t_ImportAppFromSourceControl__ul_znz_ytf_s5}

## Por Que e Quando Desempenhar Esta Tarefa

The source control integration does not support importing an application on a production instance. Instead install applications on a production instance from the application repository, an update set, or the ServiceNow Store.

## Procedimento

1. Navigate to AllSystem ApplicationsStudio.  
   The system displays the Welcome to Studio page.
2. Click Open StudioGo.  
   The system opens Studio and the Switch Applications window.
3. Click Import from Source Control.  
   Studio displays the Import from Source Control fields.
4. Enter the following field values.  
   {#t_ImportAppFromSourceControl__table_skj_zxl_s5__entry__2}

   | Field | Description |
   |-|-|
   | Network protocol | Https or ssh credential type that enables secure channel data exchange. |
   | URL | The URL to the Git repository where the application files reside. Nota: If the Git repo URL for SSH provided by your Git server does not work, check with your Git server owner or provider for the correct URL. There may be additional specifications such as scheme protocol prefixes, port numbers, and so on, required for your Git repo URL to function. |
   | Credential | Select the credential for your Git repository. (See [Getting started with Credentials](https://www.servicenow.com/docs/access?context=credentials-getting-started&version=australia&pubname=australia-platform-security&ft:locale=en-US).) Nota: If you select the ssh network protocol, enter a valid credential of the SSH Private Key type. If you select the https protocol, enter a valid credential of the Basic Auth Credentials type. |
   | Branch | The repository branch to work on within the application. Nota: The default branch is named after your instance. If you do not choose a name, the branch defaults to master. |
   | MID Server Name | Select an existing MID Server to link to a Git repository stored behind your corporate firewall. Nota: Use a separate MID Server to prevent conflicts with Discovery activities. |
   | Default email | The committer email address is defined by the sys_user record if available. But if a committer's sys_user record email field is empty, the system generates an alternate email (username@instancename.service-now.com). You can also enter a default email address and change it later. To use that default email address in all cases, select the check box. |
   [Tabela 1. Import from source control fields]

   {#t_ImportAppFromSourceControl__table_skj_zxl_s5}  
   Nota:  
   All application developers on the instance share the credential used to link a Git repository to an application.
5. Click Import.  
   The system compares the checksum in the checksum.txt file to current checksum. When the checksum values match, the integration skips validation and imports the application. When the checksum values do not match, the integration first validates and sanitizes the application files before importing them.
6. Click Select Application.  
   Studio displays the application as a new choice in the Switch Applications window.

## O que Fazer Depois

* Review the upgrade logs for any sanitization applied to application files during the import.
* Select the imported application to edit it.
{#t_ImportAppFromSourceControl__ul_zm2_lh4_kjb}
**Tópicos relacionados**   

* [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US)
* [Getting started with credentials](https://www.servicenow.com/docs/access?context=credentials-getting-started&version=australia&pubname=australia-platform-security&ft:locale=en-US)

