Skip to main content
A project is one product surface you localize — a website, a mobile app, a marketing campaign, a set of emails. It holds the translation keys, their values across languages, and project-specific settings.

​
Creating a project

From the Projects area, choose New Project and set:
  • Name — a URL slug is generated from it.
  • Source language — the language you author content in.
  • Approval required — whether changes go through the approval workflow. Can be changed later.

​
The project workspace

Inside a project the tab strip shows the primary tabs — Dashboard, Translations, and Branches (when branching is enabled) — with everything else tucked under a More menu to keep the strip uncluttered: The same More-menu pattern applies to glossaries and translation memories.

​
Languages

On the Languages tab, add the target languages this project ships in. Each becomes a column in the translation grid. The source language is fixed when the project is created and shown alongside the targets. When you remove a language, its values are removed too — export first if you want a backup.

​
Keys and values

  • A key identifies a string (e.g. home.hero.headline).
  • A value is the text for that key in one language.
Add keys manually on the Translations tab, or in bulk via Import. Keys can carry tags, a description, screenshots, and plural forms. See Translating for working with them.

​
Project settings

Settings are grouped into separate cards:
  • General — project Name, Description, and Key separator (the character used to render keys as a nested tree, default .). Edit and press Save.
  • Translation Workflow — Approval required and QA checks.
  • Translation Assistance — Use Translation Memory and Use Glossary (shown when the org has those features enabled).
  • Branching — Enable branching, plus Protect main and Require approval for merge.
  • Danger Zone — delete the project (type the project name to confirm).
Toggles in the Workflow, Assistance, and Branching cards save automatically the moment you flip them. Turning one off first asks you to confirm, spelling out what you lose — and some carry destructive side effects:
  • Turning off branching deletes ALL branches and their changes (confirmation required).
  • Turning off approval discards any in-progress proposals awaiting review and finalizes current values.

​
Members and access

The Access tab manages who can work on the project. Add members directly with project roles, or assign a team. See Roles & Permissions.
Related: Translating · Import & Export · Branches