Workspaces and projects
How an account holds your plan and billing, a workspace holds your team and projects, and a project holds your strings.
transglot organises everything in three levels.
| Level | What it is | What it holds |
|---|---|---|
| Account | Who pays. | The plan, billing and invoices, the usage allowance, and one or more workspaces. |
| Workspace | One company or one product estate. | Your team and their roles, projects, integrations, security settings and the audit log. |
| Project | One product or codebase to translate. | Keys and source strings, the source language and target languages, translations, the glossary and brand voice, and the project's tokens and keys for delivery. |
Your login is separate from all three: one login can belong to several workspaces, with a different role in each.
Accounts
Every workspace belongs to an account, and the account's plan applies to every workspace in it. An account has two kinds of people:
- Owners manage the account and hold every permission in every workspace of it. Some things only an Owner can do, such as setting up single sign-on, requiring two-factor authentication, custom branding and deleting a workspace.
- Billing members manage the plan, payment and invoices.
The account's settings show its Usage, its Owners & billing members, its Workspaces and an Account log of what changed. See Your plan and seats.
Workspaces
A workspace is where your team works. Each member has one of four built-in roles:
| Role | What it is for |
|---|---|
| Admin | Runs the workspace: members, projects, access and approvals. |
| Developer | Ships the integration: keys, languages, glossary and AI translation. |
| Reviewer | Writes and approves translations, and reviews assigned work. Cannot add keys or run AI translation. |
| Translator | Writes translations. Cannot approve their own work. |
A member can be given access to one project instead of the whole workspace, and reviewers and translators can be limited to some languages. Workspaces can also define custom roles. See Roles and what each one can do and Grant access to one project.
Projects
A project is one set of keys translated into a set of languages: typically one app, one website or one codebase. Each project has its own source language, its own target languages, its own settings for AI translation, checks and voice, and its own deploy tokens, publishable keys and CDN delivery. See Your project.
Use separate projects when the strings ship separately or need different languages, voice or reviewers. Keep strings that ship together in one project, so they share a glossary and are released together.
Limits by plan
How many workspaces, projects, languages and seats an account has depends on its plan. Free includes one workspace and one project; paid plans have no workspace or project limit. See pricing for the current figures.