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

# Members and invitations

> Invite teammates and manage their access.

Members are the people who belong to your organization. You add them by sending an email invitation with a role, and you control their access by changing their role or removing them.

Managing members requires the `members:manage` permission. Members with only `members:read` can view the member list but cannot invite, change roles, or remove anyone. See [/organizations/roles-and-permissions](/organizations/roles-and-permissions) for how roles map to permissions.

## Invite a member

Open the **Members** page in the dashboard and choose **Manage Invitations**. Enter the teammate's email address, pick a role, and select **Send Invite**.

<Steps>
  <Step title="Enter the email">
    Type the invitee's email address. It must be a valid email.
  </Step>

  <Step title="Pick a role">
    Choose the role the new member should have. The invite role picker offers **admin** and **viewer**.
  </Step>

  <Step title="Send the invite">
    Select **Send Invite**. Anyreach emails the invitee a link to accept, and the invitation appears in the pending list.
  </Step>
</Steps>

An invitation is tied to the email address you entered. The invitee accepts (or declines) from their own Anyreach account using the email address that received the invite.

<Note>
  Inviting someone does not immediately make them a member. They become a member only after they accept the invitation. Roles take effect at that point.
</Note>

## Change a role or remove a member

From the **Members** page, members with `members:manage` can:

* **Change a role** — assign a member a different organization role. The new role's permissions take effect immediately.
* **Remove a member** — revoke a member's access to the organization. They lose access right away.

Removing a member does not delete their Anyreach user account; it only removes them from this organization. If they belong to other organizations, those memberships are unaffected.

<Warning>
  Make sure at least one member keeps an admin-level role. If you change or remove the last member who can manage the organization, no one will be able to invite members, manage roles, or change billing.
</Warning>

## Invitation lifecycle

Every invitation has a status and an expiry. An invitation moves through these states:

| Status     | Meaning                                                                             |
| ---------- | ----------------------------------------------------------------------------------- |
| `Pending`  | Sent and waiting for the invitee to respond. Still actionable.                      |
| `Accepted` | The invitee accepted and is now a member. Includes when they accepted.              |
| `Revoked`  | Cancelled — either revoked by an admin or declined by the invitee. No longer valid. |
| `Expired`  | The expiry time passed before the invitee responded. No longer accept-able.         |

Each invitation carries an expiry timestamp set when it is created. Once that time passes, the invitation can no longer be accepted and is treated as `Expired`.

### Manage pending invitations

The **Manage Invitations** dialog lists all `Pending` invitations with the invitee's email and when they were invited. For each one you can:

* **Resend** — send the invitation email again. Use this if the original email was missed or lost.
* **Revoke** — cancel the invitation. A revoked invitation can no longer be accepted.

Both actions require `members:manage`.

## Accepting or declining an invitation

The invitee handles the invitation from their own account, not from yours.

When someone is invited, they see the invitation on their invitations page after signing in with the invited email address. This page shows every pending invitation across all organizations they have been invited to, so a user with invites from multiple orgs sees them in one place.

For each invitation the invitee can:

<Tabs>
  <Tab title="Accept">
    The invitee becomes a member of the organization with the role they were invited with, and is taken into that organization. The invitation status becomes `Accepted`.
  </Tab>

  <Tab title="Decline">
    The invitation is declined and becomes `Revoked`. The invitee does not join the organization. An admin can send a fresh invitation later if needed.
  </Tab>
</Tabs>

If the invitation has already expired, been revoked, or been accepted, the invitee can no longer act on it and is shown the relevant message instead of accept and decline options.

<Info>
  An invitation link is bound to the invited email address. If the invitee is signed in with a different account, they cannot accept it — they need to sign in with the address the invite was sent to.
</Info>

## Related

<CardGroup cols={2}>
  <Card title="Roles and permissions" icon="shield-halved" href="/organizations/roles-and-permissions">
    See which permissions each role grants, including `members:read` and `members:manage`.
  </Card>

  <Card title="Organizations overview" icon="building" href="/organizations/overview">
    How organizations, membership, and org context work.
  </Card>
</CardGroup>
