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

# Users and roles

Inviting your team, the four roles, and how seats work.

You work with iCustomer as a team. Members join a workspace by invitation, and what each person can do is set by their role.

## The roles

| Role       | What it means                                                                                                                                   |
| ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Owner**  | Created the workspace. Full control, including billing and credits. There is one owner, and the role cannot be reassigned from the invite flow. |
| **Admin**  | Everything but ownership: manage members, settings, and integrations.                                                                           |
| **Editor** | The working role: build audiences, run plays, act on pulses. The default for new invites.                                                       |
| **Viewer** | Read-only: see everything, change nothing.                                                                                                      |

## Inviting members

{% stepper %}
{% step %}

### Invite

Go to **Settings → Workspace → Members** and select Invite. Enter the email and pick a role (Admin, Editor, or Viewer).
{% endstep %}

{% step %}

### They accept

The invitation arrives by email and stays pending until accepted. Invitations expire if unused.
{% endstep %}

{% step %}

### They sign in

Members sign in with Google or with email and a one-time code, and land in your workspace from the workspace picker.
{% endstep %}
{% endstepper %}

## Seats

Seats follow the owner's plan; seat counts per plan live on [icustomer.ai/pricing](https://www.icustomer.ai/pricing). The Free plan is single-player; inviting members starts on a paid plan. Removing a member frees their seat.

{% hint style="info" %}
Invited members draw on the owner's credit pool as they work. Usage is recorded per member, so you can see who used what. See [Billing](/settings/billing.md).
{% endhint %}

## Outside the app

Members and roles can be managed outside the app via [API](/settings/api-keys.md) and [MCP](/iharness/bring-your-own-agent.md) as well.


---

# 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.icustomer.ai/settings/users-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.