# Organizations and teams

> How accounts, organizations and roles work on Sypnia Cloud, what each role can do, and how inviting and removing people works.

Applies to: Sypnia Cloud (paid service). Status: at launch.  
Source: https://docs.sypnia.com/cloud/organizations-and-teams/

**\[Cloud]** This page is for whoever sets up Sypnia Cloud for more than one person. None of it exists in the open-source engine, where access is decided by tokens alone. See [Projects, environments, keys and tokens](https://docs.sypnia.com/concepts/projects-keys-and-tokens).

## The three things

|                  | What it is                                                                                                      |
| ---------------- | --------------------------------------------------------------------------------------------------------------- |
| **Account**      | You. One person, one account. You sign in with your e-mail address and a password, or with your GitHub account. |
| **Organization** | What owns everything: the projects, the plan, the billing, the people and the GitHub App connection.            |
| **Team**         | The people in an organization.                                                                                  |

When you sign up, Sypnia creates your first organization, with you as its owner. One account can belong to several organizations, for example your own and a client's, and switch between them in the app. Each organization has its own plan.

There are no sub-teams at launch: **every member of an organization can see every project in it**, including its replays. If two groups must not see each other's data, use two organizations.

## Roles

Each person has exactly one role in an organization.

| What you can do                                                                      | Owner | Admin              | Member |
| ------------------------------------------------------------------------------------ | ----- | ------------------ | ------ |
| See problems, sessions, replays, traces, performance and uptime                      | Yes   | Yes                | Yes    |
| Resolve, reopen and ignore problems                                                  | Yes   | Yes                | Yes    |
| Copy the prompt, and ask for a pull request where pull requests are on               | Yes   | Yes                | Yes    |
| Receive alerts and the daily summary, and choose which                               | Yes   | Yes                | Yes    |
| Create projects, and change their settings and recording rules                       | Yes   | Yes                | No     |
| Create and revoke ingest keys and API tokens                                         | Yes   | Yes                | No     |
| Manage uptime checks, alert rules and webhooks                                       | Yes   | Yes                | No     |
| Connect a repository through the GitHub App, and turn pull requests on for a project | Yes   | Yes                | No     |
| Invite people, remove members, change roles                                          | Yes   | Yes, except owners | No     |
| Delete a person's data, a session or a problem                                       | Yes   | Yes                | No     |
| Change the plan, the payment method and billing details; see invoices                | Yes   | No                 | No     |
| Delete a project                                                                     | Yes   | No                 | No     |
| Transfer ownership, delete the organization                                          | Yes   | No                 | No     |

An organization always has at least one owner and can have several. The last owner cannot leave or lower their own role before making someone else an owner.

Changes that matter are recorded with who made them and when: resolving and ignoring problems, creating and revoking keys and tokens, changing roles, deleting data.

## Seats

A plan includes a number of people on the account. Every member counts as one seat, whatever their role, and so does every invitation that has not been accepted yet. The Free plan has one seat: you. The number of each plan is in the table of [Plans and limits](https://docs.sypnia.com/cloud/plans-and-limits).

When all seats are taken, a new invitation is refused, with a message that says so. To add someone, remove a member, cancel a pending invitation, or change the plan.

## Inviting and removing people

**To invite someone**, an owner or an admin enters their e-mail address and chooses a role. The person gets an e-mail with a link that is valid for 7 days. They accept it by signing in, or by creating an account, with that same address.

**To remove someone**, an owner or an admin removes them from the members list. They lose access at once. Their account is not deleted: it only leaves this organization.

> **Warning: Tokens outlive the person who made them**
>
> API tokens belong to a project, not to a person. A token that a removed member created keeps working, and they may still have a copy of it. When someone leaves, revoke the tokens they could read and create new ones.

## Sign-in

- E-mail and password, or GitHub sign-in.
- Single sign-on (SSO) is not available at launch. It is on the [Planned](https://docs.sypnia.com/reference/planned) page.
- Signing in with GitHub is separate from installing the Sypnia GitHub App. The first tells Sypnia who you are. The second lets Sypnia open pull requests in repositories you choose. See [The GitHub App](https://docs.sypnia.com/cloud/github-app).

## Leaving, and deleting your account

You can leave an organization at any time, unless you are its last owner. Deleting your account removes you from every organization and deletes your sign-in details. Deleting an organization deletes its projects and all their data. Both are described in [Deleting data](https://docs.sypnia.com/privacy/deleting-data).

## Example: the shop grows

The shop starts on the Free plan: one organization, one owner, one seat. When a second developer joins, the owner moves to Builder, which has more seats, and invites her as an **admin** so she can create the token for her coding agent. A freelance designer who only needs to watch replays of the checkout is invited as a **member**. Each of the three uses one seat.

When the freelancer's contract ends, the owner removes him. He had no token of his own, so nothing else needs to change.
