> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mediamonster.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Team & workspaces

> A workspace owns the plan and the credits. Invite people into it, set roles, and share one pool.

A **workspace** owns a plan, a pool of credits and a Vault. People belong to a workspace with a role. Whichever workspace you are working in is what a run is billed to, whose plan sets your limits, and whose Vault you see.

The Team page lives at [mediamonster.app/team](https://mediamonster.app/team).

## Workspaces

Every account starts with one workspace, made at sign-up and named after you. It is a workspace like any other: rename it, pick a plan for it, invite people into it. The only thing it can't do is be left or deleted, because it is where you go back to when a workspace you were invited into is gone.

Make another from the account menu behind your avatar. A new workspace has its own plan, its own pool of credits, its own Stripe customer, its own Vault allowance, and room for the people you invite. Everyone in it runs on the same balance.

The same menu switches between the workspaces you belong to.

## Seats

Cyclops and Minotaur are one person: the owner. Kraken and Behemoth seat everyone you invite. There is no per-seat charge; a team is billed on what it uses, out of the workspace's one pool of credits.

| Plan | People |
| - | - |
| Cyclops | 1 (only you) |
| Minotaur | 1 (only you) |
| Kraken | Unlimited |
| Behemoth | Unlimited |

Invitations on Cyclops and Minotaur are refused. Pick Kraken or Behemoth for the workspace first.

Guests take no seat, so you can share Vault folders with guests on any plan.

## Roles

| Role | Can do |
| - | - |
| **Owner** | Everything. Buys the plan, cancels, deletes the workspace. |
| **Admin** | Invites, removes, renames. Buys plans, credits, and Vault storage. |
| **Member** | Runs skills on the credits. Adds, edits, deletes and shares Vault files, and makes deliveries. Can't invite or buy. |
| **Viewer** | Takes a seat. Looks through the Vault and downloads from it. Can't upload, edit, delete or share. Reads deliveries but can't change them. |
| **Guest** | Takes no seat. Sees only the Vault folders shared with them, with view or edit rights. Sees no billing, no people and no deliveries, and can't spend the credits. |

Only the owner changes roles. A guest can be given a seat later, if the plan has one free.

## Invitations

On the Team page, an owner or admin adds an email and picks a role. The invitation is emailed and holds a seat until it is accepted, revoked, or expires. A guest invitation holds no seat. Pick the folders the guest will see and whether they can view or edit them.

Invitation links land on `mediamonster.app/join`. Signed-out visitors sign in or sign up first; the token is kept and the seat is taken on the next press. An invitation sent to one address must be accepted by that address.

## Guests

A guest is somebody outside the team, such as a freelancer or a client, who needs some of your files and nothing else. Invite a guest from the Team page, or from a folder's **Share folder** button in the [Vault](https://docs.mediamonster.app/vault.md#sharing-folders).

Guests sign in with a normal Mediamonster account. Once they join, the app shows them the folders shared with them and their own settings. Their own workspace is still in the account menu, and that is where their own runs are billed. A guest who can edit a folder can add, rename, tag and delete files in it. A guest can't turn on share or CDN links, and can't put files in a delivery.

## Activity

An owner or admin can open the workspace's activity from the workspace's **Settings**, at `/team/activity`. It lists everything done in the workspace — invitations sent and withdrawn, guests invited, people joining, leaving and being removed, roles changed, folders shared and unshared, the plan, credits and storage bought — newest first, with who did it and when.

The rows are the same ones each person sees on their own [account activity](https://docs.mediamonster.app/account/settings.md#activity) page: a workspace action is written to the trail of whoever did it, with the workspace on the row, so the workspace's page and the person's page read the same event. Members see their own actions on their own page and nothing of anyone else's.

## Billing

The workspace is the billing entity. The Stripe customer, the plan, the monthly credits, the top-up credits, the auto top-up arrangement, and the Vault storage blocks all live on it.

The owner may buy for a workspace, and so may an admin of a team workspace. An admin in somebody's own workspace invites and removes people but doesn't buy on their card, and the card, invoices and auto top-up are always the owner's to manage. If a plan change leaves more people in a workspace than the plan seats, nobody is removed: the owner is told, and only the owner can spend the workspace's credits until people are removed or the plan moves back up. See [Billing](https://docs.mediamonster.app/account/billing.md).

## API keys

Keys belong to the person who mints them and bill their **active** workspace at call time. Switching your active workspace switches which pool a key spends from.

The allowance and the account rate ceiling are the person's too, not the workspace's, so one teammate's busy afternoon never throttles anyone else's.

## Workspace settings

**Settings** in the **Workspace** group on the rail opens [mediamonster.app/team/settings](https://mediamonster.app/team/settings). It holds what belongs to the workspace rather than to you:

* **Workspace** — its name. The owner and admins can rename it.
* **Fields** — the Vault's own details on every file. See [Metadata](https://docs.mediamonster.app/vault.md#metadata).
* **Usage rights** — the owner's **Block expired assets** switch. See [Usage rights](https://docs.mediamonster.app/vault.md#usage-rights).
* **Single sign-on** and **Directory sync**, below.
* **Delete** or **Leave**, below.

Everyone in the workspace can read it; the owner and admins change it.

## Single sign-on and directory sync

On Kraken and Behemoth, the owner and admins can sign the team in through your identity provider and let it add and remove people. See [Single sign-on & directory sync](https://docs.mediamonster.app/account/sso.md).

## Leaving and deleting

Anyone other than the owner can leave a workspace they were invited into, guests included. Members, viewers and admins leave from Workspace settings. A guest can't open that page, so they leave from **Leave** at the foot of their Account page, shown while they are working in the workspace they are a guest of. Files you added stay in the workspace's Vault. An owner passes ownership before leaving.

**Delete workspace** is refused while a paid plan is live. Cancel the plan first, then delete. Everyone in it goes back to their own workspace. The workspace's Vault and deliveries move to the owner's own workspace. The workspace you started with can't be deleted.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.