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

# Team & roles

> Inviting users and controlling what each one can see and do.

Add your team so they work in Recepta.ai under their own login, with access scoped to what their job needs.

## Inviting users

Invite by email from **Organization**. The invitee sets their own password and joins your workspace — never share a login.

<Warning>
  Shared logins destroy your audit trail. When every action is attributed to "the office account", you can't tell who changed a price or deleted a call, and you can't revoke one person's access when they leave.
</Warning>

## Roles

Recepta.ai ships with standard roles covering the common cases, and supports custom roles when those don't fit.

<Columns cols={2}>
  <Card title="Standard roles" icon="user-shield">
    Owner and administrative roles for people who configure the system, plus operational roles for people who work calls and bookings day to day.
  </Card>

  <Card title="Custom roles" icon="sliders">
    Build a role from individual permissions when the standard set is too broad or too narrow for someone's job.
  </Card>
</Columns>

Permissions cover the areas you'd expect: company settings, billing, team management, contacts, calls, campaigns, integrations, and admin functions. Grant against the job, not the person's seniority.

## What to be careful with

<AccordionGroup>
  <Accordion title="Billing" icon="credit-card">
    Keep billing access to the people who should see and change what you pay. It's separate from configuration access for good reason.
  </Accordion>

  <Accordion title="Recordings and transcripts" icon="microphone-lines">
    Call content contains customer personal data. Grant it to people who need it for QA and support, not by default. Transcript and recording access can be granted separately — including at the [API key](/api-reference/authentication) level.
  </Accordion>

  <Accordion title="Integrations" icon="plug">
    Anyone who can disconnect an integration can stop bookings reaching your CRM. Restrict it.
  </Accordion>

  <Accordion title="Contact deletion" icon="trash">
    Deletion is not reversible. Few people need it.
  </Accordion>
</AccordionGroup>

## When someone leaves

<Steps>
  <Step title="Remove their user">
    Do it the same day. Their access ends immediately.
  </Step>

  <Step title="Check integrations they authorized">
    An OAuth connection authorized with their account can stop working when their access at the provider is revoked. Reconnect anything they owned under an account that will persist.
  </Step>

  <Step title="Rotate any API keys they created">
    Keys survive the user who made them. See [Authentication](/api-reference/authentication).
  </Step>
</Steps>

<Note>
  Running multiple [locations](/account/locations)? Access can be scoped so branch staff see their own location's calls and bookings without seeing the whole business.
</Note>