Ssnap DocsTeams
Members, roles, invitations and how teams scope everything else.
Teams are the unit of ownership in Ssnap. API keys, screenshots, subscriptions and quota
all belong to a team, never to an individual. Your account gets a personal team on
sign-up, and the team slug appears in dashboard urls: ssnap.cc/<team-slug>/dashboard.
Roles
| Role | Level | Can do |
|---|---|---|
| Owner | 3 | Everything: update and delete the team, manage members and invitations, manage billing. |
| Admin | 2 | Update the team, create and cancel invitations. |
| Member | 1 | Use the team's API keys and see its screenshots. |
Only an owner can add, update or remove members, delete the team, or manage billing. Admins handle day-to-day invitations. Owner cannot be assigned through the invitation flow; it belongs to whoever created the team.
Inviting people
Owners and admins invite by email address and role. The invitee receives an email with an accept link.
- Invitations expire after 3 days.
- Expired invitations are cleaned up automatically each day.
- A pending invitation can be cancelled from the team settings page.
- Pending invitations addressed to you appear on your dashboard.
Switching teams
If you belong to several teams, switch the current team from the dashboard. The current team decides:
- which quota and rate limit a new API key inherits,
- which team owns screenshots captured from the dashboard,
- which subscription the billing pages act on.
Leaving and deleting
- Leave removes your membership. If it was your current team, you are moved to another team you belong to.
- Delete removes the team, its memberships and its pending invitations. Members whose current team it was are moved to their personal team.
Both actions are restricted by policy: the last owner cannot simply walk away from a team that would be left without one.
Teams and the API
An API key created while team A is current stays bound to team A even if you later switch to team B. To capture against another team's quota, switch teams and create a key there.