Skip to main content
The approval workflow lets you gate translation changes so nothing goes live until a reviewer signs off. It’s the headline feature for teams that need quality control over what ships.

​
When it applies

Approval is an Approval required setting available on projects, glossaries, and translation memories — turn it on in each object’s Settings (Workflow card). When it’s off, every saved value is published immediately.
Turning approval off discards work in progress. When you disable approval, any pending proposals awaiting review are discarded and the current values are finalized as approved. You’re asked to confirm first, since it can’t be undone.

​
How it works

With approval required:
  1. A translator (a Project Editor who is not an approver) edits a value.
  2. Instead of publishing, the change is saved as a proposal with status pending review. The currently published value stays live.
  3. An approver opens the approval queue and either:
    • Approves — the proposal becomes the published, approved value, and who approved it and when is recorded.
    • Rejects — the proposal is discarded and the previous value stays.
  4. Approvers’ own edits are auto-approved — they publish directly, because an approver is implicitly trusting their own change.
This means translators can work freely without any risk of pushing unreviewed text live, while approvers retain a single place to vet everything.

​
Who can approve

Approval/rejection is available to:
  • Organization Owner
  • Organization Admin
  • Project Admin
  • Project Approver
See Roles & Permissions. To let a trusted translator self-approve, give them both Project Editor and Project Approver roles.

​
The approval queue

Approvers get a queue of all pending proposals for the project. From there you can review each proposed value against its current value and source text, and approve or reject. Bulk approval is supported so you can clear many proposals at once. Every approval writes an entry to the project’s Activity log and to the value’s history, so there’s always a record of who approved what.

​
Value statuses recap

​
Typical setups

  • Strict review — Approval required on; translators are Editors only; reviewers are Approvers. Everything is vetted.
  • Trusted team — Approval required on, but senior translators also hold the Approver role so their work self-publishes while juniors’ work is reviewed.
  • Fast / internal — Approval required off; every edit publishes immediately.
Related: Translating · Roles & Permissions · History & Rollback