Accounts & teams
An account is the namespace that owns everything you publish. Personal accounts are yours alone; organization accounts add members, roles, and a shared namespace for a team.
Accounts & namespaces
Every account has a unique slug that prefixes its resources — acme/schemas/customer, acme/bundles/common, acme/annotation-types/freshness-policy.
- Two kinds
- A personal account (one per person) and organization accounts for teams.
- The slug
- 3–25 characters, letters, numbers, and hyphens, starting with a letter or number; reserved words (about, login, docs, api, …) are taken.
- Profiles are public
- Anyone can see an account's profile — display name, bio, website, avatar. Owners edit it (the avatar included) under Settings.
Members & roles
Organization accounts have members in one of two roles. Whoever creates an organization is its first owner.
- Owner
- Manages the account — invites and removes members, changes roles, and edits settings.
- Contributor
- Publishes and maintains resources, without member-management rights.
- Last-owner guardrail
- You can't remove or demote the last owner; an organization always keeps one.
- Member emails
- An owner sees members' email addresses, and every member sees their own; the roster otherwise shows name, handle, roles, and join date.
Team visibility & invitations
Team visibility is chosen when you create an organization and isn't editable afterward in the current UI. It gates only the member roster — not the profile, and not your resources (those carry their own public or private setting).
- Public team
- Anyone can see who's on the team.
- Private team
- Only members can see the roster.
Invitations
Owners invite by email or username and assign a role. An invite stays pending until the person accepts, and owners can revoke a pending one. Invitees accept or reject in their inbox, or follow the one-time link in the invitation email (signing in or up first if needed). Invitations expire if left unanswered.