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

# Member Roles

Learn about the different roles available in organisations

## Role levels

There are 3 types of roles on the Nemo Pi platform.

<table><thead><tr><th width="180">Role</th><th>Capabilities</th></tr></thead><tbody><tr><td>Owner</td><td>Has all admin privileges, one per organization, cannot be assigned</td></tr><tr><td>Editor</td><td>Can edit the buoys and the organization settings</td></tr><tr><td>Reader</td><td>Can only view buoys and organization dashboard</td></tr></tbody></table>

Each role has a set of key capabilities as shown below. A member of your organization can be assigned exactly one of these roles.

{% hint style="warning" %}
The Owner role cannot be assigned, it belongs to the creator of the organization. We are working on a feature to transfer organization ownership. If you require ownership transfer today, please [contact us](mailto:support@nemopi.com).
{% endhint %}

When choosing a role, we encourage you to only assign the Editor role if absolutely necessary, and instead grant Reader permissions in most instances.

<table><thead><tr><th>Activity</th><th data-type="checkbox">Reader</th><th data-type="checkbox">Editor</th><th data-type="checkbox">Owner</th></tr></thead><tbody><tr><td>View Organization Dashboard</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Browse &#x26; Monitor Buoys</td><td>true</td><td>true</td><td>true</td></tr><tr><td>View Attractions (preview)</td><td>true</td><td>true</td><td>true</td></tr><tr><td>Add, Update, Delete Attractions (preview)</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Add &#x26; Update Buoys</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Invite Members to Organization</td><td>false</td><td>true</td><td>true</td></tr><tr><td>Manage Billing</td><td>false</td><td>false</td><td>true</td></tr><tr><td>Delete Buoys</td><td>false</td><td>false</td><td>true</td></tr><tr><td>Delete Organization</td><td>false</td><td>false</td><td>true</td></tr></tbody></table>


---

# 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.nemopi.com/fundamentals/accounts-and-organizations/member-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.