> For the complete documentation index, see [llms.txt](https://docs.limecall.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limecall.com/account/team-and-roles.md).

# Team & roles

Invite colleagues, set what they can do, and decide how calls are shared.

Open **Settings → Team**.

## Inviting someone

1. Open **Settings → Team**.
2. Choose to invite a member.
3. Enter their email and set their role.
4. They receive an invitation to set a password and sign in.

Invite people with their work email. Personal addresses make offboarding harder and muddle your audit trail.

## Roles

Roles decide what someone can see and change. Broadly:

**Owner** — full access, including billing and closing the account.

**Admin** — full operational access, usually including team management.

**Member** — handles calls, messages and leads. Cannot change account-wide settings.

**Viewer** — read-only. Can see conversations and reports but cannot change anything or take calls.

Give people the least access that lets them do their job. In particular, keep billing access to the people who should see invoices, and keep recording access considered — call recordings are personal data and not everyone needs them.

## Teams

Group members into teams, and route numbers to a team rather than a person. That way a departure or a holiday does not require rewiring your routing.

Set how a team rings — everyone at once, in a fixed order, or evenly distributed:

* **All at once** connects fastest.
* **Fixed order** suits seniority or specialism.
* **Even distribution** shares the load.

## Personal settings

Each member controls their own:

* **Settings → My calls** — how calls reach them.
* **Settings → My hours** — when they are available.
* **Settings → Devices** — browser, desk phone or softphone. See [Devices](/virtual-numbers/devices.md).

A member outside their own hours is not rung, even during business hours. When calls are not reaching someone, check this before anything else.

## Assignment

Conversations and leads are assigned to owners. Unassigned work is nobody's job — see [Working a conversation](/inbox-and-leads/working-a-conversation.md).

## When someone leaves

Do all of these:

1. **Reassign their open conversations and leads** before removing them, or that work disappears from everyone's queue.
2. **Check integrations they authorised.** OAuth connections — HubSpot, Slack, Google Calendar — authorised under their account stop working when it is deactivated. Reconnect under someone else's first.
3. **Revoke their devices and SIP credentials**, which otherwise keep working. See [Devices](/virtual-numbers/devices.md).
4. **Check API keys they created**, under **Settings → API keys**.
5. **Remove them** from the team.

{% hint style="warning" %}
Step 2 is the one most often missed. An integration silently stops syncing weeks later and nobody connects it to the departure.
{% endhint %}

## Seats and billing

Your plan includes a number of team members. Adding beyond that may change your bill — see [Plans & billing](/account/plans.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.limecall.com/account/team-and-roles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.