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
Find the Comments section
Scroll to the Comments section in the key detail panel. Any existing comments in the thread are shown here.
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 |