Team management controls who has access to your organization on Lingo.dev. All members share access to the organization's engines, reports, AI reviewers, and API keys.
Roles#
| Role | Permissions |
|---|---|
| Admin | Full access - manage engines, API keys, team members, billing, and all settings |
All team members are admins by default. On the Enterprise plan, Roles & Permissions replaces this default with custom roles you assign per member.
Inviting members#
Invite team members by email from the Team page in the dashboard. The invitation flow:
- Enter the email address of the person to invite
- An invitation email is sent with a secure link
- The recipient clicks the link and signs in (or creates an account)
- They are added to the organization as an admin
Via the MCP server#
You can also create invites and list pending ones from the Lingo.dev MCP server, so AI coding assistants can manage your team without leaving the conversation. When the MCP session is authenticated with OAuth, the invite email shows the inviter's name.
Invite limits
Only one pending invite per email address per organization. Invitations expire automatically - if an invite expires, you can send a new one.
Removing members#
Remove a team member from the Team page. Removing a member immediately revokes their access to the organization - they can no longer view engines, reports, or API keys.
Personal API keys created by a removed member are orphaned — they keep working only while RBAC is off (legacy behaviour); once RBAC is on they fail authorization on every engine. Rotate them before removing the user. Service API keys are unaffected: they carry their own role and engine scope and have no tie to the user who created them.
