--- title: "Editing Organizations" description: "For each Salesforce organization added to the configuration database, you can change the alias — organization name displayed in the Veeam Backup for Salesforce Web UI, edit connection settings and associate the organization woth another company." canonical: "https://helpcenter.veeam.com/docs/backup_salesforce/userguide/editing_organizations.html" breadcrumb: "User Guide > Configuring Veeam Backup for Salesforce > Managing Salesforce Organizations > Editing Organizations" dateModified: "2026-10-16" --- # Editing Organizations For each Salesforce organization added to the configuration database, you can change the alias — organization name displayed in the Veeam Backup for Salesforce Web UI, [edit connection settings](editing_connections.md) and associate the organization woth another company. ## Renaming Organizations When you connect to a Salesforce organization, Veeam Backup for Salesforce automatically collects basic organization details and uses the organization ID to create an alias. To change the alias, do the following: 1. Switch to the **Configuration** page. 2. Navigate to **Salesforce** > **Salesforce** **Orgs**. 3. Select the necessary organization and click **Rename**. 4. In the **Rename Salesforce Alias** window, specify a new name that will be displayed in the **Salesforce Alias** column of the **Salesforce** **Orgs** tab, and click **Apply**. [![Renaming Organizations](images/org_rename.png "Renaming Organizations")](images/org_rename.png){.toggle scale=60} ## Changing Company {#company} To associate an organization with another company, do the following: 1. Switch to the **Configuration** page. 2. Navigate to **Salesforce** > **Salesforce** **Orgs**. 3. Select the necessary organization, and click **Change Company**. 4. In the **Change Company** window, select the necessary company from the drop-down list and click **Apply**. ::: important If a Salesforce organization is protected by a backup policy and its data is encrypted using an AWS KMS encryption key, you will not be able to associate the organization with any other company unless the related AWS KMS account is connected to this company. To work around the issue, you can either [connect the AWS KMS account](adding_kms_connections.md) to the necessary company or [edit the backup policy settings](add_backup_policy_encryption.md) to choose a built-in encryption key instead of the AWS KMS key. ::: [![Changing Company](images/org_assign_company.png "Changing Company")](images/org_assign_company.png){.toggle scale=60}