# General Translation Platform: Reviewing and editing translations
URL: https://generaltranslation.com/en-US/docs/platform/dashboard/guides/reviewing-translations.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: How to review translations, make manual edits, and compare locales in the Dashboard.

Use the Dashboard editor to inspect generated translations, compare target locales side by side, and make precise corrections without starting a new translation job.

## Basic review workflow [#basic-review-workflow]

1. Open your project in the Dashboard.
2. Go to the **Translations** page.
3. Choose **Files** or **Components**.
4. Select or search for the content you want to review.
5. Choose the branch and locale(s).
6. Edit translations inline as needed.
7. Use annotations, history, download, and source visibility tools as needed.

## Approve translations [#approve-translations]

<Callout type="info">
  Translation approval requires an Enterprise plan. Approving a translation requires **Review & approve translations** (`translations:review:write`). Members with that permission, or who can update the project (`project:write`), can open **Project > Reviews**.
</Callout>

Completed translations are approved automatically until a member who can update the project turns **Auto approve translations** off under **Project > Settings > Review**. Changing that setting does not change existing approvals, and reviews that are already open stay on **Project > Reviews** until they are finished. That page also sets which branches need review and who reviews which translations. (See [Review settings](/docs/platform/dashboard/reference/project-settings#review)).

### Work through open reviews

1. Open **Project > Reviews**.
2. Choose **Open** or **Completed**.
3. Filter by locale and, when multiple branches are listed, by branch. Members who can update the project can also filter **Open** by **Reviewable by** and **Completed** by **Completed by**. Use **Search files** to match file names.
4. Select a review on the **Open** tab. It opens in the review editor for that language.
5. Click **Approve**, or click a **Needs review** indicator to approve a single entry. Approving the current file moves you to the next open item in that language.

Click an **Approved** indicator, or **Unapprove**, to remove an approval.

### Review one language

When files or components still need approval, **Review translations** appears under the file or component list on **Project > Translations**, with a count. Open it to work through one language on the selected branch:

1. Choose the language. Each language shows how many items still need review.
2. Open a file or **Components**.
3. Edit the translation if needed, then click **Approve**.
4. Choose **All translations** to return to the full editor.

The queue lists only items that still need review in that language. History, download, upload, and side-by-side locales stay in the full editor, where **Approve all** and **Unapprove all** apply to every reviewable locale or component in view.

### How approval works

Approving a file approves that translation for the locale. A components file is approved for a locale only when every component that requires review in that locale is approved. While **Auto approve translations** is off, removing an approval reopens the review task only if its branch matches the current review settings.

## Assign open reviews [#assign-reviews]

<Callout type="info">
  Translation approval requires an Enterprise plan. Members who can update the project (`project:write`) assign reviews and change review settings. Members with **Review & approve translations** (`translations:review:write`) can open **Project > Reviews** and see the assignee.
</Callout>

Open **Project > Settings > Review** and turn **Auto approve translations** off. **Assign automatically** appears only then, and it stays off until you turn it on. Click **Save** to keep that change.

When **Assign automatically** is on, each new open review goes to the reviewer with the fewest open reviews they can still review on that branch. Members who can update the project are never assigned this way. If no reviewer qualifies, the review stays unassigned. When a finished review opens again, a reviewer who can still review that translation keeps it.

On **Project > Reviews**, the **Assignee** column shows who has each open review. Members who can update the project can choose another reviewer who may review that translation, or **Unassigned**. The menu keeps the current assignee even after they can no longer review it. Other members see the name, or **Unassigned**, and cannot change it.

Choosing an assignee records `translation.review_assigned` in [Audit Logs](/docs/platform/dashboard/reference/audit-logs#event-records).

## Browse and find translation content [#browse-find-translation]

**Choose one or more locales** to view (in the top right). Component, keyed-file, and structured-file views can compare selected translations side by side. Raw file views show one target locale at a time.

Use **Search** to filter the current view by:

- File name
- Component name
- Key
- Source text
- Translated text

Select between two views (in the top left):

- **Files** for Markdown, JSON, gettext, Apple String Catalogs, .NET resource files, Lottie, SVG, and other file-based content.
- **Components** for React and JSX projects where strings live in UI components.

From any project page, you can also press `⌘K` on macOS or `Ctrl+K` on Windows to search across files and components. Search requires **Read translations** permission and starts after you type at least two characters. Search results link directly to the matching entry. If search fails, click **Try again**; if your access changed, refresh the page.

### Glossary and string search

The editor and the one-language review page have a side rail with **Glossary** and **String search**.

**Glossary** shows terms from the Context Groups assigned to the project. With a file open, it starts with the terms that appear **In this file**; open **Full glossary** to search every term. Choose a term to show only the entries in the open file that use it. Choose **Find in other strings** to search the project for that term, or **Open in glossary** to edit it in its Context Group. The Glossary requires **Read Org context** permission.

**String search** finds the same source text, and its translations, across the project. Select text in the open file and click **String search**, or type a word or phrase of 2 to 200 characters. Results show the source text, its translations for the locales in view, and links to matching files. String search requires **Read translations** permission.

When a translation does not reuse the same words, the editor can highlight the matching phrase. Highlighting uses platform credits from the free allowance or your credit balance; results still appear when highlighting is unavailable. (See [Usage-based billing](/docs/platform/dashboard/guides/managing-billing#usage)).

## Edit translations inline [#edit-translations-inline]

Click a translation cell to edit it. Edits are drafts until you click **Save**.

Use inline editing when you want to make precise manual changes to the existing translation.

- JSON, YAML, and Apple `.strings` files show one row per key.
- PO and POT sources show each gettext entry and the target locale's plural forms.
- Android `strings.xml` files show strings, string-array items, and the target locale's plural quantities. Resources marked `translatable="false"` are omitted.
- HTML translations show one row per translatable text run and for the `alt`, `title`, `placeholder`, `label`, `aria-label`, and `aria-description` attributes. Inline markup stays inside its text run, while `script`, `style`, and `template` content is omitted.

Use **Raw** to inspect the underlying content. The Raw view is editable for JSON, YAML, `.strings`, and `.xcstrings` translations, and read-only for HTML, PO, POT, and Android files. Saving an `.xcstrings` edit updates only the selected target locale in the catalog. SVG, `.resx`, and `.resw` files open directly in the editable raw editor and must remain well-formed XML. Use **Search in file** to find text within the open file.

Select text in the Raw editor to choose **Annotate selection**, when annotations are available for the locale, or **String search** to see how that text is translated across the project. Other views offer **String search** for selected text.

*Note: inline edits update the current translation and do not create a new entry in version history. A new version history entry is created only when source edits are sent for translation.*

## Use file tools to review [#use-file-tools]

File tools help you inspect, compare, and export translated content. They are located underneath an open filename.

Click **History** to inspect translations from previous source versions. Use it to:

- Compare translation state across source versions
- Open a prior source version and its translations
- Confirm when a translated file changed

History loads in pages for files with many versions. Search by tag, message, or version ID, then press `Enter` or leave the search field to apply it across the full history. Click **Load more** to fetch older results.

You can also:

- **Download** translated output
- Show or hide source content
- Filter by [annotation labels](/docs/platform/dashboard/guides/adding-annotations)

Lottie downloads are complete binary `.lottie` files with the translated animation reassembled into the original bundle.

SVG downloads are UTF-8 XML documents.

## Track review with annotations [#track-review-annotations]

Annotation indicators appear inside each cell: click to open the annotation panel for that entry and locale. Read more about [Annotations](/docs/platform/dashboard/guides/adding-annotations).

## Next steps

- /docs/platform/dashboard/guides/defining-context-for-translations
- /docs/platform/dashboard/guides/adding-annotations
- /docs/platform/dashboard/guides/using-ask-ai
- /docs/platform/dashboard/guides/managing-billing

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.
