> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nt3.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Comments & Collaboration

> Leave comments on translations and collaborate with your team.

Entri includes a threaded commenting system built directly into the translation editor. Comments give translators a way to ask questions about ambiguous strings and give developers a place to provide the context needed for accurate translations — all without leaving the tool.

## How Comments Work

Each translation key has its own comment thread. Threads are scoped to a specific key, so conversations stay organized alongside the string they relate to. Comments can optionally be scoped to a specific language — for example, to flag an issue specific to the French translation only.

Comments are visible to everyone on the project with at least Translator-level access. There is no separate inbox or notification center — comments appear inline in the editor, so they surface naturally as you work through translations.

## Leaving a Comment

<Steps>
  <Step title="Open a key in the editor">
    Select any key in the translation editor to expand the detail panel.
  </Step>

  <Step title="Find the Comments section">
    Scroll to the **Comments** section in the key detail panel. Any existing comments in the thread are shown here.
  </Step>

  <Step title="Type your message">
    Enter your comment in the text field. Comments support plain text.
  </Step>

  <Step title="Submit">
    Press **Enter** or click the send button to post the comment to the thread.
  </Step>
</Steps>

## Resolving Comments

Once a question has been answered or an issue has been addressed, any team member can mark the comment thread as **resolved**. Resolved threads are collapsed by default so they don't clutter the editor, but they remain accessible in the comment history.

Use resolution to signal that a discussion is complete and the translation can move forward in the workflow.

## Common Use Cases

**Translator asking for context:**

> "Does 'checkout' here refer to a shopping cart or a hotel checkout? The French translation differs."

**Developer providing guidance:**

> "This string appears in a tooltip on the billing page. Keep it under 60 characters."

**Reviewer flagging an issue:**

> "This translation uses informal language (tu). The rest of the UI uses formal (vous) — please update for consistency."

**Responding to a question:**

> "This is the shopping cart flow. The hotel checkout flow uses the key `hotel.checkout.title`."

## Permissions

| Role       | Can comment | Can resolve |
| ---------- | ----------- | ----------- |
| Owner      | Yes         | Yes         |
| Admin      | Yes         | Yes         |
| Developer  | Yes         | Yes         |
| Translator | Yes         | Yes         |
| Reviewer   | Yes         | Yes         |

All roles with project access can participate in comment threads. There is no restriction on who can resolve a comment.

<Tip>
  Use key descriptions alongside comments for context that should always be visible. Descriptions appear above the translation field and are intended for permanent guidance, while comments are better suited for questions and discussions that get resolved over time.
</Tip>