Docs

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 Cloud At launch

View as Markdown
On this page
  1. The three things
  2. Roles
  3. Seats
  4. Inviting and removing people
  5. Sign-in
  6. Leaving, and deleting your account
  7. Example: the shop grows

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.

The three things

What it is
AccountYou. One person, one account. You sign in with your e-mail address and a password, or with your GitHub account.
OrganizationWhat owns everything: the projects, the plan, the billing, the people and the GitHub App connection.
TeamThe 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 doOwnerAdminMember
See problems, sessions, replays, traces, performance and uptimeYesYesYes
Resolve, reopen and ignore problemsYesYesYes
Copy the prompt, and ask for a pull request where pull requests are onYesYesYes
Receive alerts and the daily summary, and choose whichYesYesYes
Create projects, and change their settings and recording rulesYesYesNo
Create and revoke ingest keys and API tokensYesYesNo
Manage uptime checks, alert rules and webhooksYesYesNo
Connect a repository through the GitHub App, and turn pull requests on for a projectYesYesNo
Invite people, remove members, change rolesYesYes, except ownersNo
Delete a person’s data, a session or a problemYesYesNo
Change the plan, the payment method and billing details; see invoicesYesNoNo
Delete a projectYesNoNo
Transfer ownership, delete the organizationYesNoNo

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.

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.

Sign-in

  • E-mail and password, or GitHub sign-in.
  • Single sign-on (SSO) is not available at launch. It is on the 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.

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.

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.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close