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

# Invitations

> Invite people to your organization by email and assign their role.

You add people to an organization by sending an **invitation** to their email address with a role attached. When they accept and sign in, they join with exactly the role you chose. Managing invitations is an Owner responsibility.

## How someone joins

<Steps>
  <Step title="The Owner sends an invite">
    From the members screen, the Owner enters the person's **email address** and picks a **role**. AutoSage emails them an invitation with an accept link.
  </Step>

  <Step title="They open the accept link">
    The invited person receives the email and clicks the link to accept.
  </Step>

  <Step title="They sign in — or sign up">
    They sign in with that email address, or create an account if they don't have one yet, using the same email the invitation was sent to.
  </Step>

  <Step title="They're added with the assigned role">
    Once signed in, they join the organization with the role from the invitation and can get to work.
  </Step>
</Steps>

<Note>
  The email a person signs in with must match the address the invitation was sent to. If they use a different email, ask the Owner to send a fresh invitation to the address they'll actually sign in with.
</Note>

## Good to know

<AccordionGroup>
  <Accordion title="Invitations expire after 7 days" icon="clock">
    An unused invitation expires 7 days after it's sent. If it lapses, the Owner can simply send a new one.
  </Accordion>

  <Accordion title="Owner isn't an invitable role" icon="crown">
    Because an organization has a single owner, invitations use the Billing admin, Developer, and Viewer roles. To hand over ownership, transfer it from the members screen — see [Members & roles](/teams/members-roles).
  </Accordion>

  <Accordion title="Duplicates are handled for you" icon="copy">
    Inviting someone who already has a pending invitation, or who is already a member, is handled gracefully — you won't create conflicting entries or duplicate access.
  </Accordion>

  <Accordion title="Owners can revoke anytime" icon="ban">
    The Owner can revoke a pending invitation at any time before it's accepted. Once revoked, its accept link no longer works.
  </Accordion>
</AccordionGroup>

<Tip>
  Invite each person with the **least-privileged role** that fits what they need to do — Viewer or Developer is right for most people. You can always raise a member's role later from the members screen.
</Tip>

## Next steps

<CardGroup cols={2}>
  <Card title="Members & roles" icon="user-shield" href="/teams/members-roles">
    See what each role can do before you invite.
  </Card>

  <Card title="Teams overview" icon="sitemap" href="/teams/overview">
    How organizations, environments, and tenants fit together.
  </Card>

  <Card title="Core concepts" icon="compass" href="/product/concepts">
    How knowledge bases, agents, chat, and memory relate.
  </Card>

  <Card title="Tenancy for developers" icon="code" href="/developers/concepts/tenancy">
    The API-level view of environments and tenants.
  </Card>
</CardGroup>