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

# Invite and manage organization members

Organization **Admins and Owners** can invite other members to collaborate and control which workspaces they can access. This makes it easy to give each person access only to the areas relevant to their work.

To invite a new member:

1. Go to **Organization** → **Members & roles**.
2. Click **Invite member**.
3. Enter one or more **email addresses** separated by commas or new lines.
4. Select the **role** you want to assign: Owner, Admin, Member, or Viewer.
5. Choose the **workspaces** the new member should have access to.
6. Click **Invite member**. The user will receive an invitation by email, and their membership will become active once they accept it.

Admins and Owners can also manage existing members. You can **change a member’s role**, update **which workspaces they can access**, or **remove them from the organization** when access is no longer needed.

{% hint style="info" %}
Roles have predefined permissions. Owners and Admins can manage the organization, including its workspaces, provider keys, guardrails, pricing, and members, and have full access to usage data. Members and Viewers can access the workspaces they’ve been assigned to.
{% endhint %}


---

# 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.otari.ai/how-to-guides/invite-and-manage-organization-members.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.