Documentation menu
Dashboard & analytics
Managed runners
Team & notifications
Billing & plans
Workflow files
Team and roles
Invite teammates by email or shareable link, understand Owner, Admin, and Member permissions, and manage seats.
In short
- Roles: Owner (one per workspace) > Admin (team, billing, integrations) > Member (dashboards).
- Invite by email or shareable link with role, max uses, and expiry; invites grant Admin or Member only.
- Launch includes 3 seats, Scale 5; extra seats $5/month. Developer has no team features.
The Team page shows Seats 3 / 5 and the banner 2 seats left. Add seats in Billing before you invite more than two people. The Invite tab's Invite someone form switches from Email invite to Shareable link, Admin is picked as the role, with Max uses 1 use and Expires after 7 days. Generate invite link shows Generating, then the link https://app.latchkey.dev/invite/4HNR-82QF-VM6C appears with Copy, which changes to Copied. Pending invites then lists the new link first: Admin, expires in 7 days, 0 of 1 uses, above an email invite and an older link.
Open Team in the dashboard sidebar (owners and admins) to manage who is in your workspace. The header shows your seat usage, and three tabs cover members, pending invites, and creating new invites.
Roles and permissions#
Two rules keep the hierarchy honest: Admins can only manage Members, and only the Owner can change or remove other Admins.
A pattern that works for most teams, offered as a suggestion rather than a rule: reserve Admin for the few people who actually manage billing, seats, and integrations, and default everyone else to Member. Member is not a restricted experience; members see all analytics, insights, and runner data, and the only things out of reach are team, billing, monitoring, and integration management. Since the owner can promote or demote between Admin and Member at any time, starting people as Members and promoting on need costs nothing.
The Members tab#
The Members tab lists everyone in the workspace with avatar, name, and a role badge; Pro adds email and join date. Owners and admins promote or demote between Admin and Member with an inline role dropdown, and removing a member asks for confirmation first. The page header shows how many seats are in use ("Seats X / Y").
Inviting people#
Choose between an Email invite (sent directly to one address, single-use by default) and a Shareable link (paste it in your team chat; can allow multiple uses).
Invites can grant Admin ("Can manage the team, billing and integrations") or Member ("Can view and write data"). Owner cannot be granted by invite; use Transfer ownership instead.
Choose the maximum number of uses (1, 5, 10, or 25 uses, No limit, or a custom number; 1 use by default, for an email invite or a shareable link) and an expiry (1, 3, 7, 14, or 30 days; 7 by default). Invites can be revoked any time from the Pending invites tab.
Email invites are delivered by Latchkey. Link invites give you a URL like latchkey.dev/ with a copy button.
- Delivered by Latchkey to one address
- Single-use by default
- Best when you are onboarding a specific person
- A
latchkey.dev/URL to paste in team chatinvite/ <code> - Can allow multiple uses: 1, 5, 10, 25, a custom number, or No limit (1 use by default)
- Best when a whole group needs to join at once
Pending invites#
The Pending invites tab tracks every unexpired, unaccepted invite, with a count badge on the tab itself. Each invite card shows the role it grants, an expiry countdown ("Expires in N days", "Expires tomorrow", "Expired"), and, for a shareable link with a use limit, the use count against it, for example "2 of 10 uses". A revoke button on each card lets you shut down any invite before it expires.
Invite hygiene#
A few habits, suggested rather than required, that keep invites from becoming a loose end:
- Prefer single-use email invites for individuals, and save multi-use links for genuine batches. A link forwarded beyond its intended audience is the classic way an invite ends up somewhere unexpected.
- Keep expiries short. The 7-day default is a good ceiling for links posted in chat: the conversation scrolls away, and the link should too. The options are 1, 3, 7, 14, or 30 days.
- Sweep the Pending invites tab occasionally and revoke anything that was never used.
- Invite as Member by default; the owner can promote to Admin later when the need is real.
What the invitee sees#
The invite link shows the workspace name, the role they will join as, and the expiry. If they are not signed in, they can sign in or create an account right there; after signing in, the invite is accepted automatically and they land in the dashboard. If the workspace is out of seats, they see a clear "cannot join" message and you will need to add a seat first. If the workspace's trial has ended or it has no active plan, they see why they cannot join, and the invite stays open until it expires, so they can open it again once an owner or admin chooses a plan or resolves the workspace's billing.
Signing in with an address that a teammate invited shows the Join your team prompt: Your team is already on Latchkey, then the line Join your team's workspace, or start one of your own, then one invite, acme, invited you to join as member, and an Accept button, and below it Start my own workspace instead. Accept shows a loader, and Start my own workspace instead is disabled while the invite is accepted. Then the dashboard opens on Command & Control in the acme workspace, as a member sees it in Easy: the sidebar shows acme and Sam Rivera, Member, Scale plan, without the Team and Billing rows; the title bar holds Filters, the date window and Export; and the AI Insight and Pipeline performance sections show the workspace's figures: 39 failures healed on the runner, 1 finding ready to apply of 5 open, 84% workflow health, 322 runs, an average duration of 4m 12s and a mean time to recovery of 3m.
Seats#
Launch includes 3 seats and Scale includes 5; extra seats are $5/month each. Seat usage shows in the Team header, and as you approach the limit the page warns you: "2 seats left. Add seats in Billing before you invite more than two people.", then "1 seat left. Add seats in Billing before you invite more than one person.", and at the limit "No seats left." Each banner carries Add seats, which opens Billing, where owners and admins can add seats. Removing a member frees their seat immediately.
When planning seats, count the people who need the dashboard: these are dashboard seats, gating who can sign in to view analytics and manage the workspace. Because removing a member frees the seat immediately, seats recycle cleanly when someone leaves, and at $5/month, keeping one spare seat is a cheap way to avoid a blocked invite at the worst possible moment.
Transferring ownership and leaving#
The owner can promote or demote members between Admin and Member, remove members, and use Transfer ownership to hand the workspace to another member. Transfer starts from the target member's card (the crown icon), and a confirmation dialog spells out what happens: they become the new Owner, you are demoted to Admin, and you cannot undo the action yourself. Typing TRANSFER confirms the handoff. Deleting the workspace entirely lives in Settings, Account and is owner-only.
Multiple workspaces#
You can belong to any number of workspaces (your own organization's, plus any you were invited into). The workspace menu at the head of the sidebar moves between them; each workspace has its own plan, team, repositories, and data. Latchkey remembers your last-used workspace across sign-ins.
Common questions#
Q.01Can a workspace have two Owners?
No. There is exactly one Owner per workspace: the person who installed the GitHub App, unless ownership was transferred. For a second person with full day-to-day control, grant Admin; to hand the workspace over entirely, use Transfer ownership.
Q.02Can an invite grant the Owner role?
No. Invites grant Admin or Member only. Ownership moves exclusively through Transfer ownership.
Q.03What happens if someone opens an invite when we are out of seats?
They see a clear "cannot join" message instead of joining. Add a seat first; near-limit warnings in the Team header link to billing, where owners and admins can add one.
Q.04Why can I not see the Team page?
The Team page is for owners and admins; members use the dashboards without team management. On the Developer plan, team collaboration is disabled entirely, so there is no team to manage.
Q.05Can I be in more than one workspace?
Yes, any number: your own organization's plus any you were invited into. Each has its own plan, team, repositories, and data, and the workspace menu at the head of the sidebar moves between them.