Teams
Teams let you share projects with other people, each with their own role. Teams are a paid feature — see Plans for how many teams and team members each plan allows.
Inviting people
Section titled “Inviting people”From your team’s settings, invite someone by email and role (admin, member, or viewer). This sends an email with a link to join — the invite expires after 7 days, and sending a new invite to the same address replaces the pending one with a fresh link.
To keep invite emails from being sent in bulk to someone who didn’t ask for them, resends to the same address are limited to a few per hour.
If the invite email can’t be sent, no pending invite is created — any existing invite to that address is left as-is, so it’s always safe to retry.
Owners and admins can change every project on the team. Members can change the projects they created and see the rest. Viewers can see every team project but change none of them.
A project you can see but not change is marked Read-only. You can still browse its endpoints, rules and request logs, export them, and send test requests. Controls that would change something are disabled, and fields show as plain text instead of being editable.
Accepting an invite
Section titled “Accepting an invite”An invite can only be accepted by the email address it was sent to. If you’re signed in as a different account when you open the invite link, you’ll be asked to sign out and sign back in as the invited address before you can join — this keeps team membership tied to the person who was actually invited, not just whoever holds the link.
If you’re not signed in at all, the invite page will get you there — either by signing in to an existing account or creating a new one — and bring you right back to the invite afterward.
Sending or accepting an invite is blocked once a team is at its seat cap, which counts current members plus any outstanding pending invites. At the cap, the invite form in team settings is disabled until you revoke a pending invite or remove a member. The cap comes from the team owner’s plan. See Plans for how limits are enforced.
Deleting a team
Section titled “Deleting a team”Only the team owner can delete a team. Members and pending invites are removed, but the team’s projects are not deleted — each one becomes a personal project of whoever created it.
Those projects switch to their creator’s plan right away. Limits that came from the team owner’s plan — request quotas, rate limits, log retention, and paid-only rule actions — now come from the creator’s own plan instead.
If that leaves someone with more projects than their plan allows, they keep all of them. As with downgrading, they just can’t create new projects until they’re back under the limit.