---
schema_version: "1"
id: c3679ca8269f2e719c8b9f5feefea43bebad67523a8d8de4de5d08e72c696457
title: Deploy External Client App Metadata Between Two Orgs
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/xcloud/264-0-0/deploy_external_client_app_metadata_between_two_orgs.md
canonical_url: https://help.salesforce.com/s/articleView?id=xcloud.deploy_external_client_app_metadata_between_two_orgs.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: e4345a4fdbdd7579ee2142930e7d9e1ff816b42e0851b89419e4098939ba9f50
description: Because the settings file and global settings file are separate elements of external client apps, you can update the settings file and deploy it to another org without affecting the authorization settings.
products:
  - Security
  - Cross Cloud
release: "264"
---
# Deploy External Client App Metadata Between Two Orgs

Because the settings file and global settings file are separate elements of external client apps, you can update the settings file and deploy it to another org without affecting the authorization settings.

Complete these steps to update the source org with changes that you make on org 3.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-xcloud-identity-264-0-0-production-enus/699dab6f-8f1a-4662-b24f-6521d5b747f7/images/icon_note.png)

Note If the developer org has a [namespace](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_unlocked_pkg_plan_namespaces.htm), remove references to the namespace from the external client app name in the settings files before you deploy.

1. Open the settings file on org 3, and add the full scope to the commaSeperatedOauthScopes field.
    
    ```
    <?xml version="1.0" encoding="UTF-8"?>
    <ExtlClntAppOauthSettings xmlns="http://soap.sforce.com/2006/04/metadata">
        <externalClientApplication>myeca</externalClientApplication>
        <label>myecaset</label>
        <commaSeparatedOauthScopes>Basic, Web, RefreshToken, Full</commaSeparatedOauthScopes>
    </ExtlClntAppOauthSettings>
    ```
2. Deploy these changes to org 3.
    
    ```
    sf project deploy start --manifest package.xml --target-org johndoe@example3.com
    ```
3. Retrieve the metadata files from org 3.
    
    ```
    sf project retrieve start --manifest package.xml --target-org johndoe@example3.com
    ```
4. Deploy these same files to org 1.
    
    ```
    sf project deploy start --manifest package.xml --target-org johndoe@example.com
    ```
5. Verify that the deployment succeeds. You see three files in the external client app.
    - Header file
    - Settings file
    - Policies files

- **[Initiate the Authorize Endpoint to Verify the Updated Metadata](https://help.salesforce.com/s/articleView?id=xcloud.initiate_the_authorize_endpoint_to_verify_updated_metadata.htm&release=264.0.0&type=5)**  
    Verify that the scope matches the update from one org to another.