Members & Roles
Overview
Section titled “Overview”Every person in a LokAI workspace holds a role. The role decides what they can do, and where the role is granted decides where it applies:
- A workspace role applies to the whole workspace and every project in it.
- A project role applies to one project only, on top of any workspace role the person already has.
A role can also carry a language filter, which limits language work, such as writing or approving translations, to the languages you pick.
Roles can also be given to a team, a named group of members. Everyone in the team gets the team’s roles on top of their own. See Teams.
To add someone to a workspace, invite them by email. See Inviting people.
Built-in roles
Section titled “Built-in roles”Every workspace has the same eight roles. You cannot edit them.
| Role | Where it applies | What it allows |
|---|---|---|
| Owner | Workspace | Everything, including billing and deleting the workspace. A workspace can have several owners and always has at least one. |
| Admin | Workspace | Everything an Owner can do except billing and deleting the workspace. Admins manage members, projects and settings. |
| Project Manager | Workspace or project | Manages projects and their members, languages, glossary and style guide. Reads all content. Cannot invite people to the workspace. |
| Developer | Workspace or project | Creates, edits and deletes translation keys, writes translations in the main language, and runs integrations. |
| Designer | Workspace or project | Edits existing keys (description, tags, length limits) and writes translations in the main and secondary languages. Cannot create or delete keys. |
| Translator | Workspace or project | Writes translations in any language within its language filter, including LLM-generated ones. |
| Reviewer | Workspace or project | Approves and rejects translations and customizations, and comments. Cannot edit translations directly. |
| Viewer | Workspace or project | Reads all content in scope. Cannot change anything. |
Owner and Admin only exist at workspace level, so you cannot give them on a single project.
Language filters
Section titled “Language filters”A language filter limits a role’s language work to the selected languages. Without a filter, the role covers every language.
How much a filter restricts depends on the role:
- Translator, Reviewer and Viewer: almost everything these roles do is language work, so the filter limits them to the selected languages.
- Project Manager, Designer and Developer: these roles also do work that has nothing to do with a language, such as managing project settings, members or keys. A filter only limits their translation work. Everything else still applies to the whole project. Studio marks these grants with a Language work only pill.
- Owner grants cannot have a language filter.
For example, a Project Manager on a project with a French filter manages the whole project, including its members, but can only write and approve French translations.
Manage workspace members
Section titled “Manage workspace members”Open Settings → Members. The table lists everyone with access to the workspace, and pending invitations with an Invitation pending badge. Pending invitations show only the email address. The teams each member belongs to appear under their name.
From there you can:
- Change a role: pick a new role in the member’s row. The change applies immediately.
- Remove a member: open the row menu and choose Remove from workspace. They lose access to the workspace and every project in it, including their project roles.
- Invite a member: click Invite member. See Inviting people.
- Transfer ownership (Owners only): open the member’s row menu and choose Make owner…. They become an Owner and you become an Admin. Tick Keep my Owner role to share ownership instead.
Some rows cannot be changed:
- You cannot change your own role or remove yourself.
- An Owner’s role cannot be changed, and an Owner cannot be removed, from Studio. To hand over a workspace, transfer ownership.
- An Owner can leave a workspace that has another Owner. The last Owner must transfer ownership or delete the workspace first.
| Action | Built-in roles that can do it |
|---|---|
| See Settings → Members | Owner, Admin, Viewer |
| Invite people | Owner, Admin |
| Change a role, remove a member | Owner, Admin |
| Transfer ownership | Owner |
Viewers see a banner saying they cannot change the list. Other roles don’t see the Members tab.
Manage project members
Section titled “Manage project members”Open a project, then Project Actions → Members. The page has up to three lists:
- Project members: people with a role on this project only. A Project Manager, Admin or Owner can add people, change their role or remove them. Nobody can give themselves more access than they already have: a Project Manager can make a colleague a Developer, but not themselves.
- Team access: teams with a role on this project, or on the whole workspace. Every member of the team has that role. These rows are read-only here. Change them from Settings → Teams.
- Workspace-level access: people who reach the project through their own workspace role, with a badge such as via Workspace Admin. These rows are read-only here. Change them from Settings → Members.
Owners, Admins, Viewers and the project’s Project Managers can open this page. Viewers see it read-only.
To add someone, click Add member, then pick:
- A workspace member. The list shows workspace members who don’t have a role on this project yet. Only people already in the workspace can get a project role, so invite newcomers to the workspace first.
- A role. Owner and Admin are not offered, since they only exist at workspace level.
- Optionally, Limit to specific languages and the project languages to allow.
Removing someone from a project only removes their project role. Any workspace role they hold still gives them access.
Plan limits
Section titled “Plan limits”The number of workspace members depends on your plan (members quota): 3 on Free, 10 on Pro, 50 on Team, and unlimited on Enterprise. Inviting someone checks this limit. See Plans & Limits.
Automate with the API
Section titled “Automate with the API”Roles and grants are also available through the REST API and the tRPC API. See the REST API reference.