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

# Users and roles

> Inviting, assigning roles and deactivating access.

Adding someone to your account is an administrator action with two parts: an invite, and a role. This page covers the mechanics. For what each role actually grants, see [Roles and permissions](/roles-permissions).

## Inviting someone

<Steps>
  <Step title="Open Settings → Members and teams">
    Administrators only. Select **Add agent**.
  </Step>

  <Step title="Enter their name and email">
    The email address is where their invite goes.
  </Step>

  <Step title="Choose a role">
    Pick a built-in role, or a custom role if your account has any configured. See
    [Roles and permissions](/roles-permissions) for what each one grants.
  </Step>

  <Step title="Send it">
    They get an email invite. Optionally add them to a team while you're here — see
    [Teams](/inbox/teams).
  </Step>
</Steps>

<Info>
  **A pending invite doesn't cost you a seat.** Billing starts only once the person accepts and confirms
  their account — an invite sitting unopened in someone's inbox is free. See
  [Billing and invoices](/pricing/billing).
</Info>

## Changing someone's role

Open Settings → Members and teams, edit the person, and pick a different role. This takes effect immediately — there's no approval step, and no need for them to sign back in.

## Removing access

Removing someone from Settings → Members and teams ends their seat and their ability to sign in. It does **not** delete their conversation history: past assignments, replies and internal notes stay exactly as they were, attributed to them. What you're revoking is access, not the record of what they did.

Removing a seat applies immediately, and never takes you below your plan minimum. The unused portion of the period becomes an account credit rather than a cash refund — see [Billing and invoices](/pricing/billing) for how proration works the other way, when you add someone.

## Next

<CardGroup cols={2}>
  <Card title="Roles and permissions" icon="key" href="/roles-permissions">
    The assignable roles, and when to reach for a custom one instead.
  </Card>

  <Card title="Custom roles" icon="shield-user" href="/admin/custom-roles">
    Building a permission set that doesn't fit agent or administrator.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.