Reference
Concepts & terminology
Terms used throughout the manual organized into Organization, Content, and Collaboration groups.
Look up terms here, grouped by the scenario you encounter.
Organization & people
| Term | Meaning |
|---|---|
| Organization | The billing and legal entity for members; divided into Personal and Team plans. |
| Workspace | Collaborative space under an organization housing projects, Kits, and jobs. |
| Organization member | A person belonging to the organization; roles include Owner, Admin, and Member. |
| Workspace member | A member holding specific roles inside a workspace. |
| Collaborator team | A vendor team authorized for projects to accept jobs. |
| External collaborator | Identity of vendor members within your organization; does not consume member seats. |
| Requester | The party preparing content, issuing jobs, and reviewing deliveries. |
| Vendor | The party in a collaborator team accepting jobs and translating. |
Content & versions
| Term | Meaning |
|---|---|
| Kit | A localization table inside a project containing keys, source text, translations, and custom columns. |
| Key | The identifier for a row of content in a Kit, corresponding to a UI string in your product. |
| Source language | The source text language; locked permanently once configured. |
| Target language | Languages to translate into; one column per language, flexible to add or remove anytime. |
| Custom column | Custom field holding references, character limits, or extra translator context. |
| Shared draft | Active working content currently being edited in a Kit, shared across the workspace. |
| Branch | Parallel draft streams used to prepare separate content variations simultaneously. |
| Version | An immutable snapshot committed from a draft; becomes live externally only upon Release version. |
Collaboration & delivery
| Term | Meaning |
|---|---|
| Job | A task assigning a set of keys and languages to a collaborator team, spanning acceptance to write-back. |
| Batch | Advanced feature: a bulk assignment unit from drafts to multiple teams or services (Base / Delta / Hotfix). |
| Round | Each delivery submission constitutes a round; re-delivering increments the round count while preserving history. |
| Review delivery | The review phase where requesters compare diffs against past rounds to accept or request rework. |
| Write-back | Applying accepted translations back to the Kit draft; does not produce a version. |
| Baseline version | Source text baseline frozen when a job is issued; subsequent draft edits do not alter the job. |
| Segment comments | Discussions pinned to individual segments (keys). |