# Fleet members

BalenaCloud offers the ability to collaborate with other users on the platform by inviting members to your fleets, apps or blocks and assigning them a varying degree of access as per your requirement using Member types. To invite members to your organization, refer to [organization management](https://docs.balena.io/learn/organizations#granting-access-to-fleets).

When a fleet needs to be shared with more than one user, the fleet owner can add new members. With paid accounts, it's possible to assign a level of access for a new member, based on the following types:

### Member types

| Member Type   | [Add members](https://docs.balena.io/learn/organizations#managing-roles-and-access-in-an-organization) | Delete App | Add/Remove device | Manage provisioning keys | [Device specific actions](https://docs.balena.io/learn/manage/actions) | [Tags](https://docs.balena.io/learn/manage/filters-tags) | [Variables](https://docs.balena.io/learn/manage/variables) | [SSH access](https://docs.balena.io/learn/manage/ssh-access) | [Push](https://docs.balena.io/learn/deploy/deployment) | [Configuration](https://docs.balena.io/learn/manage/configuration) | [Fleet specific actions](https://docs.balena.io/learn/manage/actions) |
| ------------- | :----------------------------------------------------------------------------------------------------: | ---------: | ----------------: | -----------------------: | ---------------------------------------------------------------------: | -------------------------------------------------------: | ---------------------------------------------------------: | -----------------------------------------------------------: | -----------------------------------------------------: | -----------------------------------------------------------------: | --------------------------------------------------------------------: |
| Administrator |                                                   Yes                                                  |        Yes |               Yes |                      Yes |                                                                    Yes |                                                      Yes |                                                        Yes |                                                          Yes |                                                    Yes |                                                                Yes |                                                                   Yes |
| Developer     |                                                   No                                                   |         No |               Yes |                      Yes |                                                                    Yes |                                                      Yes |                                                        Yes |                                                          Yes |                                                    Yes |                                                                Yes |                                                                   Yes |
| Operator      |                                                   No                                                   |         No |               Yes |                      Yes |                                                                    Yes |                                                      Yes |                                                        Yes |                                                          Yes |                                                     No |                                                                 No |                                                                    No |
| Observer      |                                                   No                                                   |         No |                No |                       No |                                                                     No |                                                       No |                                                         No |                                                           No |                                                     No |                                                                 No |                                                                    No |

#### Administrator

A new fleet in balenaCloud can only be created by an [administrator](https://docs.balena.io/learn/organizations#managing-roles-and-access-in-an-organization) of an organization. Administrators are the only users who can add other fleet members or delete the fleet. Learn more about the [administrator role](https://docs.balena.io/learn/organizations#managing-roles-and-access-in-an-organization) in an organization.

#### Observer

Observers are given read-only access to the fleet and its devices. They are not able to modify, add, or remove any devices, nor are they able to perform device actions. This role can only be assigned by fleet owners on paid plans.

#### Operator

Operators have all the access given to observers, plus the ability to manage a fleet's devices. This means operators can add and remove devices, generate & revoke provisioning API keys, perform device actions, and modify device tags, metadata, and environment variables. Operators also have full [SSH access](https://docs.balena.io/learn/manage/ssh-access) to the fleet's devices. This role can only be assigned by fleet owners on paid plans.

#### Developer

Developers are given, in addition to the access provided to operators, the ability to manage fleet software. This includes creating new releases, modifying fleet variables, and downloading balenaOS images. This role is the closest to a fleet owner—developers can do everything owners can except for deleting the fleet or adding new members. The Developer role can be assigned by fleet owners on free or paid accounts.

### Add a fleet member

To add a new member to your fleet, click on the *Members* tab of the fleet:

<figure><img src="https://2252285266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQ348GwFntj7HlWYI0v4%2Fuploads%2Fgit-blob-fa906ad857de8ecc394d60bd6bff33a0c5fa10cd%2Fmembers_tab.webp?alt=media" alt=""><figcaption></figcaption></figure>

This brings up a list of all fleet members, if any have been assigned. Click on the *Add member* button in the top left:

<figure><img src="https://2252285266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQ348GwFntj7HlWYI0v4%2Fuploads%2Fgit-blob-c0699a9c36991daaea1669c0f37d4c567d26d4f0%2Fadd_member.webp?alt=media" alt=""><figcaption></figcaption></figure>

The *Add member* dialog has a dropdown with descriptions of the member types, as well as information about which types are available based on your billing plan. Choose a level of access, then enter the username or email address of the new member:

<figure><img src="https://2252285266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQ348GwFntj7HlWYI0v4%2Fuploads%2Fgit-blob-955efc7945e9db5c5a8d7ec1f75939d72469d6d9%2Fmember_dialog.webp?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
Fleet members must have already signed up for a balena account before they can be added to a fleet.
{% endhint %}

After you click *Add*, you will see the username of the new member in the list. From here, you can edit access levels or remove the user if necessary:

<figure><img src="https://2252285266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQ348GwFntj7HlWYI0v4%2Fuploads%2Fgit-blob-d5b314821235bed63c69d8117623023bb420f361%2Fmember_list.webp?alt=media" alt=""><figcaption></figcaption></figure>

All users that have been added to a fleet will see that fleet in their dashboard, with an indicator to designate it has been shared by the fleet owner:

<figure><img src="https://2252285266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyQ348GwFntj7HlWYI0v4%2Fuploads%2Fgit-blob-5f73a05b3fafd2b9d104315edaef85c29b1030a8%2Fshared_app.webp?alt=media" alt=""><figcaption></figcaption></figure>

Fleet members will have the option to remove themselves from a fleet by clicking on the members tab, selecting the checkbox by their name from the member list, clicking on the *Modify* button, and selecting *Delete member*.

{% hint style="danger" %}
If you remove your member access to a fleet, you will not be able to undo the action. Only the fleet owner will be able to restore your access.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.balena.io/learn/accounts/fleet-members.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
