> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aireadyscore.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

# Team members and invitations

> How people join your organisation: domain matching and owner-sent invitations.

There are two ways a colleague ends up in your organisation: they sign in with a matching
work-email domain, or an owner or admin invites them by email.

## Joining by domain

Membership is anchored to your organisation's verified work-email domain. When someone
signs in at `/login` with an email on that domain, they join your organisation as a
**member**, no approval queue. The first person on a new organisation becomes its
**owner**.

<Note>
  If your organisation has automatic joining turned off, a matching domain is not enough:
  the person sees **Automatic joining is disabled**, *"This organisation is protected by
  an administrator and cannot be joined automatically."* In that case an owner or admin
  invitation is the way in.
</Note>

## Inviting your team

Owners and admins can invite colleagues from **Organisation → Members**,
*"Everyone in your organisation."*

<Steps>
  <Step title="Open the invite dialog">
    Select the invite action on the Members page.
  </Step>

  <Step title="Add addresses and roles">
    Add up to 10 rows. You type only the part before the @, the address always ends in
    your organisation's verified domain, invitations are domain-locked. Choose a role for
    each: owners can grant **Member** or **Admin**; admins can grant **Member** only. (No
    one can invite an owner.) Then select **Send invitations**.

    Your plan includes a set number of **seats** (active members plus pending
    invitations). If a batch would go over, it's refused with *"No seats are
    available for your organisation right now."* — remove a pending invitation
    that's no longer needed, or contact support to add seats. Re-sending an
    existing pending invitation never uses a seat.
  </Step>

  <Step title="They sign in">
    Each invitee gets an email and signs in at `/login` with that address, using the
    one-time code or their Google Workspace / Microsoft 365 account. They land in your
    organisation with the role you chose.
  </Step>
</Steps>

## Pending invitations

Sent invitations appear in their own card on the Members page until they are used, each
with visible **Resend** and **Revoke** actions: resending refreshes the invitation's
expiry (*"Invitation resent."*); revoking (*"Invitation revoked."*) means the address can
no longer use it. Pending invitations also surface as a dashboard alert so they are not
forgotten. If an invitation email fails to send, the page says so, and the recorded
invitation still applies when the person signs in with that address.

<Note>
  Invitations add people to your organisation with a chosen role. They are not needed for
  ordinary joining, anyone on your verified domain can simply sign in.
</Note>

## Roles at a glance

Owners can do everything, including managing advisors and organisation settings. Admins
manage the team and day-to-day setup. Members complete assessments and see results. The
full breakdown is in [Roles](/accounts/roles).

## Related

<CardGroup cols={2}>
  <Card title="Signing in" href="/accounts/signing-in" icon="right-to-bracket">
    One-time codes, Google Workspace, and Microsoft 365.
  </Card>

  <Card title="Roles" href="/accounts/roles" icon="user-shield">
    What owners, admins, and members can each do.
  </Card>
</CardGroup>