> For the complete documentation index, see [llms.txt](https://docs.m-xr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.m-xr.com/marso-studio/getting-started/organisations.md).

# Organisations

An **organisation** groups your team together in Marso Studio, with a shared credit balance everyone can draw from. One person creates it, then invites colleagues by email.

You don't need an organisation to use Marso Studio — if you're working on your own, you can skip this page.

## Before you start

**Everyone needs an M-XR account before they can be invited.** Invitations go to an email address that already has an account, so ask your colleagues to sign up first — an invitation can't create an account for them.

To create an account, go to [marso.app](https://marso.app) and sign up. Once your account exists, the organisation settings are in your profile area.

## Creating an organisation

1. In Marso Studio, click your **profile** in the bottom-left corner, then click **Settings**.
2. Click **Organisation** in the left-hand menu.
3. Create your organisation and give it a name.

Whoever creates the organisation is its **owner**.

## Inviting people

In the same **Organisation** settings area:

1. Enter the email address of the person you want to add.
2. Click **Invite**.

Repeat for each person. Use the email address they signed up with — an invitation sent to an address without an M-XR account won't reach anyone.

## Accepting an invitation

If you've been invited:

1. Create your account at [marso.app](https://marso.app), if you don't have one already.
2. Open Marso Studio at [marso.app](https://marso.app).
3. Click your **profile** in the bottom-left corner → **Settings** → **Organisation**.
4. Accept your invitation.

## Roles

|                                        | Owner | Admin | Member |
| -------------------------------------- | ----- | ----- | ------ |
| Owns the account                       | ✅     | —     | —      |
| View the organisation's credit balance | ✅     | ✅     | —      |
| Spend the organisation's credits       | ✅     | ✅     | ✅      |

Every member can spend from the shared balance, whether or not they can see what's in it.

**Changing the owner** isn't something you can do yourself — the current owner needs to email **<support@m-xr.com>**.

## Using organisation credits

A new organisation starts with a balance of **0**. Organisation credits are held separately from your personal credits, so creating or joining an organisation doesn't move your own balance across.

To spend the organisation's credits instead of your own, open the **Credits** area and **toggle to your organisation**. Everything you generate from then on draws from the shared balance.

See [Credits & billing](/marso-studio/reference/credits-and-billing.md) for what each step costs.


---

# 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.m-xr.com/marso-studio/getting-started/organisations.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.