Workspaces and members
Understand AI Glot workspace ownership, member roles, shared credits, API keys and the permission ceiling applied to personal OAuth connections.
A workspace is the boundary around translations, glossaries, credits, billing, members and developer credentials. Data from one workspace is never intentionally exposed to another.
Roles
| Role | Typical access |
|---|---|
| Admin | Manage the workspace, members, billing and workspace API keys |
| Member | Use the translation platform within the access granted by the workspace |
Admins invite teammates from Team in the sidebar, by sharing an invite link. Joining adds the person to the existing workspace; it does not copy data into a personal account. The Free plan has a single seat, so inviting teammates needs a paid plan.
- Role. Each person is an admin or a member. Admins open the menu beside a member to change their role or remove them from the workspace.
- Invite link. Create the link, copy it and send it to a teammate. Anyone who has the link can join until the expiry date shown under it. Use the link’s menu to rotate it, which stops the old link working immediately, or to disable invites.
- Member API access. The most each member may grant to an AI client or CLI login of their own. Admins can make an exception for one person with Change. See Developer access.
Developer access
Workspace API keys are created by admins in Developer tools, on the API tab. A key belongs to the workspace rather than to one person and can be named, scoped, rotated and revoked.
OAuth connections, such as a CLI login or an MCP client, carry the identity of the member who approved them. The workspace’s member access policy acts as a ceiling: a person limited to read-only developer access cannot obtain write access by requesting a broader OAuth scope. Admins set the workspace default in the Permissions tab of Developer tools. A new workspace starts with every scope allowed, while workspaces created before 31 August 2026 keep the ceiling they already had.
The ceiling only limits what a member can hand to an AI client or the CLI. It does not stop a member from doing the same things by hand in the app, and it does not apply to workspace API keys, which only admins can create.
Leaving or deleting
Removing a member removes their workspace access. Revoking a key or OAuth connection stops that credential independently. Account deletion and workspace ownership have safeguards so shared workspace data is not silently orphaned.
Personal preferences
Members can update their display name, theme and interface language from their profile settings. Email subscriptions are managed separately so product updates, activity notifications and account or billing emails can be controlled independently.
