Translating

Zero-Touch Localization (Strings)

Available for

  • Team, Professional, Business, Enterprise and Software UI/UX plans

Get in touch with Sales for licensing questions.

Zero-touch localization automates the full localization pipeline for a connected code repository. It detects new or changed strings, creates and routes a translation job, translates the content, and pushes the translated strings back to the repository, without any manual steps in between.

How It Works

Zero-touch localization connects three existing Strings features into a single automated pipeline:

  1. Repo Sync watches the connected repository. When a pull request adds or changes strings, Repo Sync imports the new and updated keys into the project.

  2. Automated Job Creation (AJC) creates a translation job for the imported keys, using a connected job template.

  3. The job template's pre-translation setting translates the keys using machine translation (or translation memory matches, if configured).

  4. Once the job is complete, Repo Sync exports the translated strings back to the same pull request.

Each stage runs on the settings and integrations already configured for the project. Zero-touch localization does not introduce a separate translation engine or job type. It coordinates the existing ones automatically.

Important

Zero-touch localization only works with a Repo Sync connection to a GitHub repository, set up through the GitHub App. Repo Sync connections made with a personal access token, and Repo Sync connections to GitLab or Bitbucket, are not supported for zero-touch localization.

The Zero-Touch Tab

Zero-touch localization is managed from a dedicated Zero-touch tab in the project view. The tab reflects one of three states for the project:

  • Enable zero-touch localization: Zero-touch localization has not been enabled for the project.

  • Active: Enabled, with a healthy Repo Sync and Job Automation, and all required project settings in place.

  • Error: Enabled, but something the pipeline depends on is missing or broken.

Permissions

Enabling, fixing, or turning off zero-touch localization requires permission to manage project settings:

  • Strings Owners and Administrators can manage zero-touch localization in every project.

  • Project Managers can manage zero-touch localization only in projects to which they are assigned.

  • Developers, Designers, Translators, and Guests cannot manage zero-touch localization.

Enable Zero-Touch Localization

To enable zero-touch localization for a project, follow these steps:

  1. Open the project and go to the Zero-touch tab.

  2. Click Enable zero-touch localization.

    The Enable zero-touch localization window opens listing the project settings that zero-touch localization will affect. Review the affected settings first to make sure the changes do not disrupt another workflow. All pre-selected settings must be enabled for zero-touch localization to work.

  3. Click Enable to proceed.

    The Zero-touch tab for the project opens, showing the full configuration.

  4. If a project already has a qualifying Repo Sync and Job Automation set up outside the Zero-touch tab, they are detected automatically. Skip the next two steps. Otherwise, continue with the next steps to set them up.

  5. Set up a Repo Sync by clicking the Configure repo sync button.

    The GitHub sync window opens. The connection type is pre-selected as Github app and Automatic import is set to From open pull requests. These options must remain as is to enable zero-touch localization.

  6. Set up a Job Automation by clicking the Create job automation button.

    The Add automation window opens. The Include branches option is selected and the Trigger is set to Upload Batch. These options must remain as is to enable zero-touch localization.

  7. Once both Repo Sync and Job Automation are correctly configured, the Zero-touch tab shows the project's status as active, denoted by a green checkmark.

Errors and Fixes

An error appears on the Zero-touch tab when a required project setting was changed outside the tab. It also appears when the connected Repo Sync or Job Automation was deleted, paused, or is otherwise unhealthy. The tab identifies which part is affected:

  • For a project setting that was turned off elsewhere, use the fix action shown in the tab to turn it back on.

  • For a missing or broken Repo Sync or Job Automation, follow the link shown in the tab to create a replacement.

Details about the error are displayed on the integration's own page. Once the underlying issue is resolved, the project returns to the active state automatically.

Turn Off Zero-Touch Localization

To turn off zero-touch localization for a project, follow these steps:

  1. Open the project and go to the Zero-touch tab.

  2. Toggle the configuration off.

Turning it off pauses the connected Repo Sync and Job Automation. The Zero-touch tab then shows the project as not configured. General project settings that zero-touch localization uses are not changed.

Limits

Zero-touch localization project limits depend on the plan:

  • Business and Enterprise plans support zero-touch localization on an unlimited number of projects.

  • Team, Professional, and Software UI/UX plans support zero-touch localization on up to two projects.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.