Skip to main content
Every translation in Entri has a status that tracks where it is in your review and approval workflow. Statuses let teams coordinate between translators, reviewers, and developers — and they control what gets included in exports.

Status overview

┌───────────────┐     translated      ┌────────────────┐
│  Untranslated │ ──────────────────▶ │   Translated   │
└───────────────┘                     └────────────────┘

                                          reviewed


                                      ┌────────────────┐
                                      │    Reviewed    │
                                      └────────────────┘

                                          approved


                                      ┌────────────────┐
                                      │    Approved    │◀── Translation Memory
                                      └────────────────┘

Status definitions

Untranslated

No value has been set for this key/language pair. The translation editor highlights these keys so translators know where to start.

Translated

A value exists but has not been reviewed. This is the default status after a human types a translation or AI generates one. Needs a human review before it can proceed.

Reviewed

A reviewer has checked the translation for accuracy, tone, and consistency with the glossary. It is ready to be approved.

Approved

The final approved state. Approved translations are included in exports, counted as complete in analytics, and automatically added to Translation Memory.

How statuses are set

Human translation

When a translator types or edits a value in the editor, the status becomes Translated.

AI translation

Translations generated by nt3 translate or the in-app AI feature start with the Translated status. AI translations are never automatically approved — they always require a human review step.

Reviewer action

A user with the Reviewer or Admin role can change a translation’s status to Reviewed or Approved directly in the editor using the status dropdown or keyboard shortcut.

Bulk status changes

From the translation editor’s filter view, you can select multiple keys and change their status in bulk — useful when approving a batch after a translation sprint.

Status and exports

The nt3 pull command downloads translations for all statuses by default, giving you the most complete picture of your translations at any time. Approved-only exports are available through the REST API and web UI export feature, which is useful for production builds where you only want reviewed content.

Status and Translation Memory

Only Approved translations are added to Translation Memory. This ensures the TM contains only high-quality, human-verified strings that are safe to reuse across projects.
Build a habit of approving translations before merging to your main branch. Approved translations power the TM, improving AI translation quality over time for your entire organization.

Role permissions

Different team roles can advance the workflow to different stages:
RoleCan set TranslatedCan set ReviewedCan set Approved
TranslatorYesNoNo
ReviewerYesYesYes
DeveloperYesYesYes
AdminYesYesYes
OwnerYesYesYes

Filtering by status

In the translation editor, use the status filter to focus on a specific stage:
  • Show untranslated — find missing translations to fill in
  • Show translated — find AI or human translations waiting for review
  • Show reviewed — find translations ready for final approval
  • Show approved — verify what is included in the next export

Reverting status

If an approved translation needs to be updated after a source string changes, editing the translation value automatically resets its status to Translated, flagging it for re-review. You can also manually change any status in the dropdown without editing the text.