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

# Team & invitations

> Invite colleagues, accept email invitations, and understand who can change settings.

Clausum is multi-user. Your organization administrator invites people by email; each person completes MFA and lands in the dashboard with a role that controls what they can change.

## Accepting an invitation

<Steps>
  <Step title="Open the email">
    Invitations come from Clausum with a secure link to `/invite/[token]`.
  </Step>

  <Step title="Create or sign in">
    New users set a password; existing users authenticate.
  </Step>

  <Step title="Set up MFA">
    Required for dashboard access in enterprise deployments.
  </Step>

  <Step title="Land in the workspace">
    You arrive in the merchant dashboard (cases, protection, transactions) for your organization.
  </Step>
</Steps>

<Warning>
  Invitation links expire. If yours expired, ask an **admin** in your organization to resend from **Equipo**.
</Warning>

## Inviting teammates (merchant organization)

Admins (and roles with team write access) can invite from **Equipo** (`/dashboard/team`):

1. Enter email and role (**admin**, **analyst**, or **viewer**)
2. Send invitation — Clausum emails the activation link
3. Pending invites appear until accepted or revoked

Pending invitations are reconciled automatically when the user already has access (no stuck “pending” state after first login).

## Roles at a glance

See [Roles & permissions](/concepts/roles-and-permissions) for the full matrix. Summary:

| Role        | Typical use                         |
| ----------- | ----------------------------------- |
| **Admin**   | Keys, rules, team invites, settings |
| **Analyst** | Cases, transactions, simulations    |
| **Viewer**  | Read-only monitoring                |

Some enterprise deployments restrict who may invite users — if you do not see **Invitar**, your role is read-only by policy.

## Managed onboarding (enterprise)

Financial institutions and partners provisioned by Clausum may receive:

* A first admin invite from Clausum operations
* Optional **invite-only** signup (`enterprise invite only` mode)

In that model, self-service signup is disabled; your operations contact provisions the workspace and sends the first invitation. Day-to-day team invites still happen inside **Equipo** once you are in.

## Security hygiene

* Do not forward invitation emails outside your company
* Revoke departed users from **Equipo**
* Rotate API keys in **Integraciones** when staff with key access leave

<CardGroup cols={2}>
  <Card title="API keys" icon="key" href="/guides/api-keys">
    Create checkout and server keys after onboarding.
  </Card>

  <Card title="Access & environments" icon="globe" href="/concepts/access-and-environments">
    Sandbox URL and API base URL policy.
  </Card>
</CardGroup>