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

# Members and roles

Invite people to your organization and control what they can do.

## Roles

| Role                   | What they can do                                                        |
| ---------------------- | ----------------------------------------------------------------------- |
| **Owner**              | Everything. The owner is the person who created the organization.       |
| **Organization Admin** | Everything in the organization, including managing members and settings |
| **Member**             | What the organization's member permissions allow (see below)            |

### Member permissions

For members, each feature has a permission level: **none**, **read** or **write**. The features include:

Notebooks, folders, threads, superagents, agent sessions (chats), reports, DAGs, apps, deployed APIs, exports, executor images, members, roles, self-hosting and block restrictions.

So, for example, an organization can let members create notebooks and threads but only view superagents, or not see deployments at all.

## Adding people

Admins can add people in two ways.

| Method              | How it works                                                                                                                                       |
| ------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Invite by email** | Enter someone's email address and choose their role. If they don't have a Zerve account yet, the invitation is waiting for them when they sign up. |
| **Invitation link** | Share a link that anyone can use to join. Each organization has two links: one that joins as an **Admin** and one that joins as a **Member**.      |

{% hint style="warning" %}
Share the Admin invitation link carefully: anyone who uses it gets full access to your organization.
{% endhint %}

## Removing people

When you remove a member, **both invitation links are reset automatically**, so the old links stop working. Anyone you want to invite afterwards needs a new link.

## How many people can join

| Plan                 | Limit                             |
| -------------------- | --------------------------------- |
| **Free** and **Pro** | Up to 10 members                  |
| **Team**             | The number of seats you've bought |

On Team plans, each person uses one seat in the organization. See [Plans, credits and billing](/zerve-docs/administration/plans-credits-and-billing.md#seats).

## People outside your organization

You can share individual pieces of work with people who aren't members. Read access doesn't need a seat; write access does. See [Sharing and privacy](/zerve-docs/administration/sharing-and-privacy.md#sharing-with-people-outside-your-organization).


---

# 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.zerve.ai/zerve-docs/administration/members-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.