One Leed login can belong to any number of workspaces. This page covers getting into somebody else’s — the invitation link, the screen it opens, and what you may still need from them afterwards — and then moving between the workspaces you already belong to. If nobody has invited you and you want a workspace of your own, Creating Your Account starts from an empty form instead.
Accepting an invitation
An invitation arrives as an email with the subject You’ve been invited to join {workspace} on Leed and a single Accept Invitation → button. The button opens /auth/accept-invitation/<invitation-id> in your browser, and that one URL renders four different screens depending on the state of the invitation and whether you are signed in.
flowchart TD
A[Open the invitation link] --> B{Which screen appears?}
B -->|Invalid Invitation| C[Ask the sender for a fresh invitation]
B -->|Invitation Already Used| D[It was accepted, rejected or cancelled — ask for a fresh one]
B -->|Join the workspace| E{Do you already have a Leed account?}
E -->|Yes| F[Sign In to Accept]
E -->|No| G[Create Your Account]
G --> H[Verify your email address]
F --> I[Back on the invitation, now signed in]
H --> I
I --> J[Accept Invitation]
J --> K[Leed opens the workspace]
A live invitation is titled Join
- I already have an account
- I am new to Leed
Choose Sign In to Accept. Leed sends you to the sign-in screen with the invitation remembered, so once you have followed your magic link — or signed in with Google or GitHub — you come straight back to the invitation rather than to the workspace you were already in. The screen now reads “You’re joining {workspace}.” with a single Accept Invitation button.
Signing in from an invitation is the ordinary sign-in flow with nothing special about it; Signing In covers the four methods and which one you get.
Choose Create Your Account. The form is deliberately short — First Name, Last Name, Email, the “verify you are human” challenge, and a Sign up with Google button above the divider. It asks for no site title and no domain, because you are joining a workspace that already exists rather than creating one.
Submitting it sends you a verification email, exactly as an ordinary sign-up does. Clicking the link in that email brings you back to the invitation, signed in, with the Accept Invitation button waiting.
| What the screen says | Why | What to do |
|---|---|---|
| Join | The invitation is live and you are signed out | Take whichever of the two paths above applies to you |
| Join | The invitation is live and you are already signed in | Press Accept Invitation |
| Invitation Already Used — “This invitation has already been {status}.” | The invitation is no longer pending: it was accepted, rejected or canceled | Ask whoever invited you to send a new one |
| Invalid Invitation — “This invitation is invalid or has expired.” | The id in the link does not resolve, or the invitation has aged out | Ask for a new one; invitations expire after about two days |
| “Failed to accept invitation.” | The accept request itself failed | Reload the page and try once more; if it repeats, tell the person who invited you |
What role you arrive with
Whoever invited you chose a role when they sent the invitation, and Roles and Permissions explains what each of the six can do.
Accepting the invitation adds you to the workspace’s membership, but it does not by itself finish creating your account inside the CMS. In practice that means a successful accept can still be followed by a permission refusal on your first request — and an administrator, not you, is the one who clears it.
Administrators send, resend and revoke invitations from Inviting People, which is the other half of this flow.
Belonging to more than one workspace
Everything about you is attached to your login and follows you everywhere. Everything about the work is attached to a single workspace and does not.
| Belongs to your login | Belongs to each workspace |
|---|---|
| Your email address, which is also your sign-in identity | Your role in that workspace |
| Your profile — name, photo, title, bio, handles | Every page, asset, form and contact |
| The list of sessions on your Security tab | The team, and everyone’s roles and overrides |
| Your API tokens | The plan, the limits and the billing |
| Your connected GitHub account | The site, its domain and its deployments |
Because your profile is one record rather than one per workspace, editing your bio in one workspace changes the byline everywhere — see Your Profile. Plans are the mirror image: each workspace has its own, so Plans and Tiers is a per-workspace question, never a per-person one.
The organization picker
The Select Organization screen lists one card per workspace you belong to, each with its logo (or the first letter of its name), the workspace name and its identifier. Choosing a card sets it as your active workspace and reloads Leed into it.
If you belong to no workspaces, you get No Organizations instead, with the line “You don’t belong to any organizations yet.” and a Create Company button that starts a fresh sign-up. That state usually means an invitation has not been completed, or that your last membership was removed.
Switching workspaces
Switch Organization in the profile menu — the avatar at the bottom of the rail — takes you back to the picker. The entry appears only when you belong to more than one workspace, so if you cannot find it, you have one.
Switching is a full page reload, not a tab change. Leed reloads deliberately: every list, every menu, every count and every permission you were looking at was scoped to the workspace you are leaving, and a partial refresh would leave stale data on screen. The practical consequence is that anything half-typed into a form is lost, so finish or abandon what you are doing before you switch.
When Leed asks you to choose
Sometimes Leed sends you to the picker without being asked. That happens when a request cannot be attributed to a workspace — you belong to several and none of them is currently active, typically after a session was created outside the browser or an active workspace was removed. Picking one resolves it.
Three screens are exempt, because each manages the choice itself: the picker, the sign-in screen, and the application-authorization screen (which has its own Workspace to authorize field, described in Authorizing Devices and Clients). Bouncing those screens to the picker would throw away the sign-in or connection they were in the middle of.
Leaving a workspace
There is no self-service control for leaving. Removal is done by an administrator from the team screen, and it takes effect on your next request.
If the workspace you are removed from was your only one, Leed can no longer place you and you land on No Organizations. Your login, your profile, your sessions and your API tokens all survive — what you have lost is the membership, not the account.