Orgs and teams
A person has an account: their personal space, with a handle at quorumcal.com/{handle}. Handles are shared with orgs and team aliases, so each is unique.
An org is a group of people with central settings: members and roles, billing, the policies for tokens and connected apps, and webhooks. An org owns nothing schedulable itself.
A team sits directly under an org (teams are flat: no subteams). Teams own booking links, polls and recurring series. Because a team owns them, they survive people leaving and are managed by the team’s admins. A team’s address is quorumcal.com/{org}/{team}/{link}. An org admin can give a team a root alias (quorumcal.com/gdgc/...) or the root publishing permission, which lets its links also appear at quorumcal.com/{org}/{link}.
| Role | Where | Can |
|---|---|---|
| Owner | org | Everything an admin can, plus transfer or end the org. There is exactly one. |
| Admin | org | Manage members, invites, teams, policies, webhooks and every team’s links. |
| Team admin | team | Manage that team’s links, members and bookings. |
| Member | org, team | Use the team’s polls and series, see their own bookings. |
A credential never exceeds its owner’s role, whatever scopes it holds. Things you may not see answer 404, not 403, so handles and slugs don’t leak.
Where this shows up in the API
Section titled “Where this shows up in the API”- Personal:
/v1/me/..., CLI commands without a prefix (links create). - A team’s:
/v1/orgs/{handle}/teams/{teamPath}/..., CLIteam ...commands. - An org’s:
/v1/orgs/{handle}/..., CLIorgs ...commands (members, invites, policies, webhooks).