Teams

A team is a shared workspace — projects, channels, endpoints, events, and billing are all scoped to the team, and every invited member gets full access. Teams are a Scale plan feature; on Hobby, Hacker, and Pro you work in your personal workspace alone.

Every account has a personal workspace by default. You can have both a personal workspace and membership in one or more teams, and switch between them from the workspace switcher in the top of the sidebar.

When to use a team

• You’re collaborating — more than one person manages the same Slack/webhook/email channels.
• Shared billing — one invoice covers the whole org, not per-seat.
• Handoffs matter — a teammate needs to pick up replays, endpoint config, or rules without transferring ownership of an account.

If you’re a solo operator, the personal workspace is lighter and cheaper. Upgrade to a team when a second person needs access.

Creating a team

Open the workspace switcher in the top-left of the sidebar and choose Create organization. Name it, confirm, and you land in the new team as its owner. The new team starts on the Hobby plan — enough to use it as a solo workspace but inviting members requires upgrading to Scale first (see below).

Roles

Two roles today:

Members can do everything operational — create channels, configure endpoints, write rules, replay events. They can’t change plan, open the billing portal, or invite more people. Ownership transfers happen by promoting another member in team settings, then (optionally) demoting yourself.

Inviting members

From Team → Members, click Invite member and enter an email address. Invitees receive a link; clicking it walks them through signup (if they don’t have an account yet) and drops them into the team as members.

Scale gate

Every invitation is gated on the team being on the Scale plan. On Hobby/Hacker/Pro the invite UI shows an inline banner directing you to upgrade the team first. This is the core team feature — multi-seat access requires Scale.

Team size cap: 20 members per team today. Contact us if you need more.

Removing members

Owners remove members from Team → Members. When a member is removed:

• Their access to the team workspace ends immediately — the dashboard signs them out of the team context.
• Any API keys that member created are automatically revoked. Keys stop authenticating on the next request; open streams close within about a minute. This closes the usual offboarding hole where a saved token outlives the person.
• Projects, channels, endpoints, and rules they authored remain on the team. Ownership of resources lives with the team, not the individual.
• Audit log entries for their past actions stay on the team’s log.

If a specific API key needs to survive a member’s departure, create it under a different member (or under the owner account) before the removal.

Billing

Billing lives at the team level. When the active workspace is a team:

• Team owners see the full billing page and can upgrade, open the Stripe portal, or cancel.
• Members see plan + usage but get an explanatory notice instead of the upgrade controls.
• One Stripe customer per team — members don’t have their own subscription for team usage.

Personal workspaces keep their own separate billing. Switching between personal and team means switching plans, quotas, and usage views in one click.

Resources are team-scoped

When a team is the active workspace:

• Projects, channels, endpoints, API keys, rules, events, threads — everything is owned by the team.
• Any member can create, edit, and delete any of these.
• Switching back to the personal workspace shows only that user’s personal resources; the team’s stay put.

There’s no cross-workspace sharing — a project in Team A can’t be moved to Team B or to personal. If you need the same resource in two places, re-create it.

Leaving or deleting a team

• Members can leave a team from their account settings. Their own personal workspace is unaffected.
• Owners can delete the team entirely (from the Team settings area, coming soon). Deleting cascades — every project, channel, endpoint, rule, event the team owned is purged; the team’s Stripe subscription is cancelled on Stripe’s side via the billing portal.

If you’re the sole owner and want to leave, promote another member to owner first — teams must always have at least one owner.

Plan availability

Being a member of a team has no plan requirement — only creating a team that invites others does.

Related

• Billing — pricing details.
• Team settings — the dashboard surface.