Workspaces and roles
One workspace per customer. Profiles, glossaries, uploaded files, runs and reports belong to a single workspace. One workspace cannot read another's.
Five roles
What someone sees follows their role. A translator gets Run and Reports (their own runs). A linguist adds Compare, Profiles, LQA and Eval. A PM and a quality lead add Integrations, Connections and the Workspace, Quality and Security and data tabs; a quality lead can also assign a profile's owner and edit any profile. An admin adds Plan and usage, Members, AI review, Developer and Branding. An admin also reads the workspace's audit trail and downloads it as CSV through the API (Audit trail). An admin also sets the workspace's retention.
| Area | Admin | Quality lead | PM | Linguist | Translator |
|---|---|---|---|---|---|
| Run a check | yes | yes | yes | yes | yes |
| Reports | yes | yes | yes | yes | own runs |
| Profiles, view | yes | yes | yes | yes | no |
| Profiles, edit | yes | yes | yes | owner only | no |
| LQA and Eval | yes | yes | yes | yes | no |
| Analytics | yes | yes | yes | yes | no |
| Integrations and Connections | yes | yes | yes | no | no |
| Workspace settings | yes | yes | yes | no | no |
| Members and branding | yes | no | no | no | no |
| AI review, models and providers | yes | no | no | no | no |
| API keys and webhooks | yes, Team and up | no | no | no | no |
Hiding a page is a courtesy. Every permission is checked again on the server, so a hand-typed address returns a refusal rather than data.
A profile's owner
Any member, in any role, can be named the owner of a profile and may then do everything a PM can to that one profile. Profiles.
Roles and plans
Roles come with Team and up. On Free and Solo the one seat is the admin.
Modules
A module your workspace has not bought (LQA, Eval) is not there for anyone, whatever their role. LQA is included in Business and set up with you; Eval is on request for Enterprise.