Inviting People

The Invite Member button sits in the header of Settings → Team Members and is rendered only for Administrators. What it does is straightforward — an email goes out, the person follows a link, they join your organization at the role you chose, and they appear on Team Members. This page walks through each step, what your invitee sees along the way, and the one place the role you picked is described differently.

Inviting is free on every plan. Users are unlimited on Free, Starter and Growth alike, so there is no seat count to watch and no upgrade prompt at the end of this flow.

Sending an invitation

1. Open Settings → Team Members and choose Invite Member. The Invite Team Member dialog opens, described as “Send an invitation email to add someone to your organization.”
2. Type the person’s address into Email Address.
3. Pick a Role. The select lists all six roles by their display names: Administrator, Content Publisher, Content Approver, Content Writer, Read Only, Restricted. Read Roles and Permissions before you open the dialog — this is the role your invitee joins with.
4. Choose Send Invitation. The dialog closes and a notification confirms “Invitation sent to” followed by the address.

If you are bringing in an outside contributor, invite them as Restricted and open exactly the content they need with Resource-Level Access Overrides. A Restricted member sees almost nothing until you grant it, which is a much better starting point than trimming back a role that was too generous.

What your invitee receives

The email arrives from Leed with the subject “You’ve been invited to join <organization> on Leed”. It names the person who invited them, names your organization, and carries a single Accept Invitation → button pointing at /auth/accept-invitation/<invitationId>.

One detail worth expecting, because it looks like a bug and is not: the email describes the invitee’s role as member (or admin, if you chose Administrator). That is the organization-management role, not the Leed role you picked — which still travels with the invitation and is the one they receive. The role you pick in the dialog explains the difference.

Accepting an invitation

The link opens Join <organization>, which reads “<inviter> invited you to join <organization>.” What happens from there depends on whether they already have a Leed account.

There are five states that link can be in, and each shows different copy:

If they already have a Leed account

1. They choose Sign In to Accept and sign in as they normally would.
2. They land back on the same Join screen, now signed in.
3. They choose Accept Invitation. Leed creates their membership at the role you chose, switches their session to your workspace and reloads into it. If the accept is refused, the screen changes to Invalid Invitation with the message “Failed to accept invitation.” and a Go to sign in link; opening the invitation link again brings back the Accept Invitation button so they can retry.

If they are new

1. They choose Create Your Account, which opens the invited sign-up form.
2. They fill in first name, last name and email, clear the anti-bot check, and choose Create Account — or take the Sign up with Google shortcut and skip the form entirely.
3. Leed sends them a verification email; verifying it returns them to the accept screen, where they finish with Accept Invitation.

Invitations that no longer work

Two states end the flow early, and both are worth recognizing by their exact wording so you can tell them apart from a sign-in problem:

• “This invitation is invalid or has expired.” — the link is not resolvable. Either it has passed its expiry window or the invitation was revoked.
• “Invitation Already Used — This invitation has already been <status>.” — the invitation exists but is no longer pending; it was accepted, rejected or canceled.

Both screens offer a Go to sign in link and nothing else. The fix for either is a fresh invitation from your side, not anything the invitee can do.

Pending invitations

While an invitation is outstanding, it appears in the Pending Invitations block above the member list. The block lists pending invitations only and is hidden entirely when there are none, so its absence means nothing is waiting on an answer — not that something failed to load.

An invitation leaves the block as soon as it is no longer pending: an accepted one is now a member and appears in the member list below, and a rejected or revoked one needs no action. Invitations expire after roughly two days. That window comes from the underlying authentication library’s default rather than from a Leed setting, so treat the (expired) marker on the row as the authority rather than counting hours yourself — and choose Resend to bring an expired invitation back to life.

The role you pick in the dialog

Two roles travel with every invitation, and only one of them is the one your invitee gets.

The Role select offers all six Leed roles, and the one you pick is stored on the invitation and applied when it is accepted. Alongside it, Leed derives the organization-management role from your choice: Administrator becomes admin, and every other role becomes member. That second value is what the invitation email names, and it governs only inviting, removing and updating the organization. An invitation sent before Leed began storing the Leed role falls back to Administrator for admin and Read Only for everything else.

Accepting an invitation creates both the invitee’s organization membership and the CMS member record that carries their Leed role, so they appear on Settings → Team Members straight away. Someone who was a member before and was removed is brought back at the invited role. If the CMS record cannot be written, the accept is refused rather than half-done, and the invitee can simply try again.

The sequence, end to end:

sequenceDiagram
    autonumber
    actor Admin as Administrator
    participant CMS as Settings → Team Members
    participant Auth as Organization records
    actor Invitee
    Admin->>CMS: Invite Member — email + Leed role
    Note over CMS,Auth: The Leed role is stored on the invitation.<br/>admin / member is derived from it.
    CMS->>Auth: create invitation (Leed role + admin or member)
    Auth->>Invitee: "You've been invited to join …" email
    Invitee->>Auth: follow the link, sign in or sign up, Accept Invitation
    Auth->>CMS: create the CMS member record at the invited Leed role
    Auth-->>Auth: organization membership created
    CMS-->>Invitee: session switched to the workspace at the intended role

Once they have joined, Managing Team Members is where an Administrator changes their role and where you tick Billing or Developer access if they need it. Your invitee’s side of all this — signing in, the organization picker, and belonging to more than one workspace — is covered in Joining and Switching Workspaces.

Adding someone without an invitation

There is a second way in, and it is worth naming so that an administrator hunting the interface for a “New user” button stops hunting: there is no such button. Leed has an Administrator-only API for creating a member directly — it creates the CMS member record, the login and the organization membership together, so the person can sign in by email afterwards — but it is not wired to any control in the CMS today. The screen that would have hosted it exists in the codebase and renders nothing.

In practice that means every route into a workspace currently goes through the invitation flow above, or through a direct API call by someone comfortable making one.