# Teams and invites

- URL: https://getroomi.com/docs/teams
- Built: 2026-10-26

A workspace is what owns projects and is on a plan. This page covers your own
workspace and a team, how you make a team and invite someone into it with a
link, what owners and members can do, and how you move between workspaces.

Team seats come with the Team plan, for 2 to 5 people, and with Enterprise,
by arrangement, for more.

## Workspaces

Everything you make belongs to a workspace: projects, builds, pages, viewer
links, and everything viewers did in your rooms. The plan, its limits and its
usage are the workspace's, not a person's: a project a member creates counts
against the workspace's allowance, and so do their deploys.

There are two kinds:

- **Your own workspace**, made the first time you sign in, named after you,
  with you as its owner. Nobody else is ever in it. Its plans are Free and
  Pro.
- **A team**: a workspace you share with other people, with its own projects,
  links and viewers, its own name and brand, and its own plan, on Team or
  Enterprise, which its owners manage. Nothing in it comes from anyone's own
  workspace.

Each workspace is isolated from every other: every request is scoped to the
workspace you are working in, and asking for another workspace's project,
link or feedback by its id is answered "not found". See [Security and
privacy](https://getroomi.com/docs/security).

## Making a team

In **Settings**, **Workspace**, the **Teams** panel takes a name, up to 80
characters, and **Make a team** makes it; **Create team…** in the workspace
menu at the top of the side bar does the same. You become its owner, and the
app moves you into it. Your own workspace stays as it is.

A new team has no plan, so it holds no projects and has no seats beyond yours
until it has Team or Enterprise. Choose Team, with its seats, in
**Settings**, **Billing** ([Plans and limits](https://getroomi.com/docs/plans#buying-a-paid-plan)).
More than 5 people is Enterprise, by arrangement: contact sales. While you
own a team with no plan, you cannot make another.

## The People panel

In a team, **Settings**, **Workspace**, has a **People** panel listing:

- **Members**: each person's name, email and role, **Owner** or **Member**.
  You are marked **You**.
- **Invites** still waiting, shown to its owners: the email each is for,
  marked **Waiting to accept**, when it expires, and **Cancel invite**.

Beside the title, the panel counts the seats used, invitations still waiting
included. Its owners also see the invite form, while a seat is free, and
**Make owner** or **Make member** and **Remove** beside everyone else.

In your own workspace the panel says that nobody else is ever in it.

## Inviting someone

1. In **Settings**, **Workspace**, under **People**, enter their email address
   and choose **Make an invite link**.
2. Copy the link and send it to them yourself, however you like.

The link:

- works once;
- works only for a person signed in with an account whose email is the one you
  invited, so a forwarded link is no use to anyone else;
- expires 7 days after it was made.

While it waits, the invite is listed in the panel, and it holds a seat. Everyone invited joins as a member; an owner can make them an
owner afterwards.

## Accepting an invite

The link opens the app's invite page. Sign in with the account whose email was
invited, if you are not already, and the page says who invited you, and to
which team. **Join it** makes you a member and switches the app to that team.

If the page says "This invite is not for the account you are signed in with,
or it has expired, been revoked or been used. Sign in with the email it was
for, or ask for a new link.", check which account you are signed in with, or
ask for a new link.

## Roles

A team has two roles. The person who makes it is its first **owner**, and the
people invited join as **members**. A team always keeps an owner.

| | Owner | Member |
|---|---|---|
| Deploy, make links, arrange rooms, read analytics and feedback, work the pipeline | Yes | Yes |
| See who is in the team, and the plan and its usage | Yes | Yes |
| Make and cancel invites | Yes | No |
| Make someone an owner or a member, or remove them | Yes | No |
| Rename the team, and set the brand its rooms wear | Yes | No |
| Choose the plan, pay for it and see its invoices | Yes | No |
| Delete the team | Yes | No |
| Move one of its projects to another workspace | Yes | No |
| Leave the team | While another owner stays | Yes |

Inside the team, a member can do everything an owner can with its projects:
the platform scopes its data to the workspace, not to the person.

**Remove** beside a member asks first, then takes them off the team: they stop
seeing its projects, viewers and feedback at once. What they made stays: their
builds remain, shown as by "someone no longer in this workspace". A connector
they approved for the team stops at its next call, which is refused as "no
longer a member of that workspace". Their own workspace is unaffected, and
they can be invited again.

Removing a member ends their access at once, in the app, in `roomi` and through
the connector: the platform checks membership on every request, so a session
they already had open answers them as a stranger from their next request.
Team seats are held by the platform too: without them, an invite is refused
however it is asked for, and one made earlier cannot be accepted once the plan
has none.

## Moving a project to another workspace

A project can move from one workspace you belong to into another: from your
own workspace into a team, say. In the project's **Settings**, **Danger zone**,
**Move to another workspace** lists only the workspaces you are in; choose
one and **Review the move**. Nothing has moved yet: the app says what goes
with it, what viewers would see differently (the name the room shows, the
brand it wears), who is told, and anything that stops it. **Move it** moves it.

- Everything goes with it: builds, links, viewers, visits, feedback, the
  pipeline, bookings, pages, files, the community card and its own domain.
- Every link you have sent keeps opening the same room, at the same address.
- A move that would stop one of them, silence its own domain, or take the
  other workspace past its plan is refused, and the app says what would need
  to change.
- Nothing is refunded or charged: the project counts towards the new
  workspace's plan from then on.
- The people of both workspaces are told; you are not.

Moving a project out of a team needs one of its owners; moving one in, any
member. Claude can do the same through `move_project`
([Claude and MCP](https://getroomi.com/docs/mcp#move-project)).

## Leaving or deleting a team

**Settings**, **Danger zone**, in a team:

- **Leave team**: you stop seeing its projects, viewers and feedback, and its
  owners can invite you again. An owner can leave only while another owner
  stays: make someone else an owner first, or delete the team.
- **Delete team**, for its owners: deletes its name, brand, people and
  invitations, once it holds no project and its plan is cancelled, with its
  name typed again to confirm. Everyone in it keeps their own workspace.

Your own workspace is never left.

## Moving between workspaces

Once you belong to more than one workspace, **Settings**, **Workspace**, shows
**Your workspaces**, marking the **Current** one, with **Switch to it** beside
each of the others; the workspace menu at the top of the side bar switches
too. Switching changes what every screen of the app shows.

Where your other tools act:

- **The app** acts in the current workspace.
- **Claude's connector** acts in the workspace that was current when you
  approved it. Its team tools (`list_workspaces`, `list_members`,
  `invite_member` and the rest) name the workspace they act on, so one
  connection can manage every team you own. See [MCP tools](https://getroomi.com/docs/mcp).
- **`roomi`** acts in the workspace its sign-in started in, which is the first
  one you joined: for most people, their own.

> [!NOTE]
> Every workspace starts on Free, and moves to Pro or Team whenever you like, in Settings, Billing. Sign in at app.getroomi.com with GitHub or Google, then add the connector to Claude at https://mcp.getroomi.com/mcp, or run the CLI with npx @getroomi/cli. These pages describe the connector, the CLI, pitch.json, the app and the room as they are.
