> 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.md).

# Accounts & Organizations

Nemo Pi allows you to create an account to manage your smart buoy. Organisations allow your team to share management of your smart buoy.

{% hint style="info" %}
Buoys must be attached to an organisation. So even if you are **the only person** managing a buoy, you will be required to create an organisation (free).
{% endhint %}

## What is your Account?

Creating your account is the first step to registering and managing your Nemo Pi. At the moment, the only way to sign up is **via** **an existing GitHub** or **Google account.** We chose to do so to ensure new users would have a safe authentication and authorisation mechanism.

{% content-ref url="/pages/GHb5MYHnvZn7PMgyyqCp" %}
[Creating an Account](/fundamentals/accounts-and-organizations/creating-an-account.md)
{% endcontent-ref %}

## What is an Organisation?

An organization is a group of users who can access the same buoys. You can create an organization for your dive school or research group for example. Organisations have a minimum of 1 user and must be created regardless of whether or not you are the only person managing a buoy. This is because **every buoy must be associated with an organisation.**

{% content-ref url="/pages/kwj34n1WfyMRtQe6BFvW" %}
[Creating an Organization](/fundamentals/accounts-and-organizations/creating-an-organization.md)
{% endcontent-ref %}

Depending on the number of members, smart buoys, and mooring buoys, you may choose to upgrade your organization to a monthly or yearly subscription plan. By default, every organization is free to begin with.

### Inviting and Removing Members to Organisations

Users in an organisation are considered members. You can invite members by:

{% content-ref url="/pages/L30RJs9FdddhYMYMzPaF" %}
[Inviting Members](/fundamentals/accounts-and-organizations/inviting-members.md)
{% endcontent-ref %}

You also have the ability to remove members if they are no longer part of the organisation or require access to the buoy.

{% content-ref url="/pages/IDkad8BSMP40ar9uyOOh" %}
[Removing Members](/fundamentals/accounts-and-organizations/removing-members.md)
{% endcontent-ref %}

### Managing Member Access Control

It's important for organisations to have the ability to manage their users and what sort of access they have to the buoys they manage. This is a vital security layer and done through Role-Based Access Control (RBAC).

{% hint style="info" %}
When you create an organisation, you automatically become the Owner
{% endhint %}

RBAC is a method of managing and regulating access to resources based on the roles assigned to individual users or groups. This means if you are responsible for administering multiple groups of buoys that require different people to be involved in a team, you can assign appropriate access. For example, you may be responsible for two different organisations with overlapping members. Some members only need read-only access to both organisations while others need the ability to edit dashboards. As an owner in your company's organisation, you can assign members the appropriate roles in each organisation. 

{% content-ref url="/pages/PF1WRdbhDvM32EsLVE8w" %}
[Member Roles](/fundamentals/accounts-and-organizations/member-roles.md)
{% endcontent-ref %}


---

# 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.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.