> For the complete documentation index, see [llms.txt](https://www.bluegamma.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.bluegamma.io/documentation/account-and-team-management/adding-and-removing-seats.md).

# Adding and Removing Seats

How organisation admins invite people, change their access, remove and add back members, and request more seats in Organisation settings.

Organisation admins manage who uses BlueGamma on the organisation's plan in **Organisation settings**. From there you can invite people, change their access, remove them, add them back and request more seats.

{% hint style="info" %}
Organisation settings replaced the old Admin Dashboard in October 2026. Old links to the **Admin** page now open Organisation settings.
{% endhint %}

## Opening Organisation settings

1. Log in at [app.bluegamma.io](https://app.bluegamma.io).
2. Open the account menu at the bottom of the sidebar (your name and email).
3. Under **Organisations**, click your organisation. Only admins can open it from here.

The page has two tabs, **Members** and **General**. The header shows whether the organisation is on a paid plan or a trial (**Paid** or **Trial**) and your own access level.

## Access levels

| Access         | What it means                                           | Takes a seat? |
| -------------- | ------------------------------------------------------- | ------------- |
| **Member**     | Uses BlueGamma.                                         | Yes           |
| **Admin user** | Uses BlueGamma and manages the team.                    | Yes           |
| **Admin**      | Manages the team and seats only. Doesn't use BlueGamma. | No            |

Admin users and admins can invite and remove people, change access and request seats. An **Admin** who doesn't use BlueGamma only sees Organisation settings.

## Checking your seats

At the top of the **Members** tab, the seat meter shows **X of Y seats used**, with how many members you have and how many seats are held by pending invites. When every seat is in use, the meter says so, and you need to free a seat or request more before inviting anyone else who uses BlueGamma.

On a trial organisation there is no seat limit yet: the meter shows the number of members, and each member uses their own trial until the organisation buys seats.

## The members list

The **Members** sub-tab lists everyone in the organisation. Use **Search name or email** to find someone, and click a column header to sort.

| Column          | What it shows                                                                                                      |
| --------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Member**      | Name and email. **(you)** marks your own row, and **· external** marks someone outside your admins' email domains. |
| **Access**      | **Member**, **Admin user** or **Admin**.                                                                           |
| **Last active** | When they last signed in. **Inactive** appears when someone hasn't signed in for more than 60 days, or never has.  |
| **First seen**  | When they signed up or joined.                                                                                     |

## Inviting people

1. On the **Members** tab, click **Invite people**.
2. Under **Email addresses**, enter one or more addresses. You can paste several at once. Any email domain works, so you can invite advisers and consultants.
3. Under **Access**, choose **Member**, **Admin user** or **Admin**.
4. Click **Send invite**.

The dialog shows how many of your free seats the invites will use. If there aren't enough, remove someone or click **request more seats**. You can still invite an **Admin** who doesn't use BlueGamma when no seats are free.

Each person receives an email invitation. They accept it by signing in, or creating an account, with the invited email address, then clicking **Accept** on the **Invitations** page. Personal, academic and +alias email addresses can't sign up to BlueGamma, so invite people at their work address.

Admins can also open the same dialog from anywhere in the app: open the account menu and click **Invite colleague**.

### Pending invites

The **Pending invites** sub-tab lists invitations that haven't been accepted yet, with the access level and when each was sent. Invites for a **Member** or **Admin user** count towards your seats while they are pending.

* Click **Resend** to send the invitation email again.
* Click **Revoke** to cancel the invitation.

## Requesting more seats

1. On the **Members** tab, click **Request more seats** (on a trial organisation, **Talk to us about seats**).
2. Enter how many more seats you need, and add a note if you like.
3. Click **Send request**. We'll get back to you about pricing.

## Changing someone's access

In the **Access** column, click a person's access level and choose a new one. Giving someone admin rights asks you to confirm with **Make admin**, and you stay an admin too. Changing someone to **Admin** frees their seat, because they no longer use BlueGamma.

You can't change your own access.

## Removing people

1. On the **Members** sub-tab, find the person.
2. Click the **⋯** menu at the end of their row and choose **Remove from organisation**.
3. Confirm with **Remove**.

To remove several people at once, tick their checkboxes and click the **Remove** button that appears above the list (for example **Remove 3 people**).

When you remove someone:

* They lose access to your organisation on BlueGamma.
* Their work stays with your team, and their seat becomes available for someone else.
* They can still sign in with a free personal account.
* They move to the **Removed** sub-tab, and you can add them back at any time.

You can remove anyone except yourself. To leave the organisation yourself, see [Leaving an organisation](#leaving-an-organisation).

## Adding people back

The **Removed** sub-tab lists everyone who has been removed, and when. Click **Add back** next to a person, or tick several and click the **Add back** button above the list (for example **Add back 2**). People you add back rejoin as a **Member** and take a seat, so you need a free seat for each.

## Exporting the member list

On the **Members** sub-tab, click **Export to Excel** to download everyone in the organisation, including removed people. The **Users** sheet lists each person's name, email, access, status (Active or Removed), first seen and last login dates, and the date they were removed.

## Renaming the organisation

On the **General** tab, edit **Organisation name** and click **Save**.

## Leaving an organisation

Anyone in an organisation can leave it, admins included. On the **General** tab, click **Leave** followed by your organisation's name, then confirm with **Leave**. Admins can also choose **Leave organisation** from the **⋯** menu on their own row of the members list.

You keep your BlueGamma login and your personal swaps, but lose the organisation's plan and its shared swaps, entities and API keys, which stay with the organisation. An admin has to invite you to come back. If you are the only admin, make someone else an admin first.

## What members see

Members who aren't admins see the organisation's name and their access level in the account menu, but can't manage members or settings. If they open Organisation settings, they see a short note that they are a member and the option to leave the organisation. Ask one of your organisation's admins for any changes.

## Frequently Asked Questions

### How do I become an admin?

Ask an existing admin to change your access to **Admin user** or **Admin**. If nobody in your organisation can do this, email <support@bluegamma.io>.

### How do I accept an invitation?

When an invitation is waiting, the account menu shows **Invitations** with a count. Open it and click **Accept** or **Decline**.

### I'm not in an organisation. How do I set one up for my team?

Open the account menu and click **Set up a team account**. Tell us how many people need access, add a note if you like, and click **Send request**. We'll get back to you about pricing.

For anything else, email <support@bluegamma.io>.


---

# 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://www.bluegamma.io/documentation/account-and-team-management/adding-and-removing-seats.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.
