Team roles & tokens
Org admin, member, viewer and billing roles, invites that carry a role, GitHub sign-in with zero extra scopes, instant per-token revocation.
Four roles. The org admin, the person who created the team, and anyone they promote, manages who is in it, their roles, the plan and the team itself. Member runs checks and manages connections, tokens, policy and notifications, but not the membership or the bill. Viewer sees everything and changes nothing, for the engineer who needs to read the run log without being able to touch a connection. Billing manages the subscription and nothing else. Invites carry the role the invitee will get.
Sign-in is GitHub with zero extra scopes: identity only, never repository access. Team tokens (blv_…) are what CI uses; each one records where it was last used, its first use and every new address are audit events, and each one is revoked individually and instantly, every rotation lands in the audit log too.
The CLI is open source and needs no account: npx bolvrk check migration.sql