<aside>

Description

The Deploy Metadata feature pushes completed translations from SimpleTranslate back into a Salesforce org. Deployment writes selected translations to the Salesforce Translation Workbench, with control over which items are included.

</aside>

Prerequisites

• Metadata has been translated in SimpleTranslate (see Translate Metadata).
• The Org Credential is valid and the integration user has deploy permissions (see Salesforce User Permissions).

Steps

Deploy a single metadata item

1. Open the Metadata Translator section in the navigation bar.
2. Locate the metadata item in the table.
3. Click the action on the desired metadata row and select deploy.

Deploy multiple metadata items

1. Check the boxes for the metadata rows you want to deploy.
2. The Deploy button appears above the list.
3. Click Deploy to push all selected translations to Salesforce.

What to expect

• Deployment can take a few minutes depending on how many items you selected.
• Once deployment finishes, the translations are live in Salesforce under the Translation Workbench.
• You can verify the deployment by checking the translated labels in your Salesforce org.
• Deploying the same item again will overwrite the previous translation in Salesforce.

Deployment permissions

Each Salesforce environment has a deployable setting that controls who is allowed to push translations to it. This is separate from translation access — being able to translate does not automatically mean being able to deploy.

• When an environment is marked as Deployable, all eligible users (Admins, Owners, Developers) can deploy to it.
• When an environment is marked as Not deployable, deployment is restricted. Admins can then add specific users to an allowlist — only those users can deploy to that environment, no one else.
• Users with the Translator role can never deploy, regardless of environment settings.
• Permissions are configured per environment. Granting deploy access on one environment (for example, Sandbox) does not grant access on another (for example, Production).

Configure deployment permissions

1. Open the Org Credentials section.

2. On the environment row, click on the Edit Environment(pen) dialog.

3. Toggle the environment between Deployable and Not deployable.

4. If the environment is set to Not deployable, use the user dropdown to add the people who should be allowed to deploy. Each user appears with their name, email, and role.

   

5. To revoke access, click the trash icon next to a deployer. The change takes effect immediately.

What admins should know

• Non-admin users can open the Deployment Permissions dialog to see who is authorized, but cannot make changes.
• When an environment is set to Not deployable, a yellow “Deployment is restricted” warning appears inline on the environment row with a direct link to the permissions dialog.
• When deploying a job that targets multiple environments, the user must have deploy permission on every selected environment. If they are blocked on even one, the deploy action is disabled for the entire job.
• Every add and remove is recorded in an append-only audit trail (action, target user, performing admin, timestamp) for compliance review.

Troubleshooting

• If deployment fails, confirm the Org Credential is still valid and the integration user has API and metadata deploy access.
• If some items fail while others succeed, check the error details for permission or validation issues on specific metadata types.
• If deployed translations do not appear in Salesforce, confirm the target language is enabled in your Salesforce Translation Workbench settings.

<aside>

Quick View

End User Documentation

• SimpleTranslate
• SimpleT AI
• Organization </aside>