Everything in Canner is owned by an organization, not by a person. Membership is how a person gets to act on that organization’s projects, domains, data and billing. You manage it at Organization (under Settings), where an admin can invite, edit and remove users.
Two roles
Admin has full control — users, billing, the plan, and every project and area. An organization always keeps at least one admin: the last one can’t be removed or demoted, so someone can always manage billing and people.
Member starts with no access. You grant exactly what they need — nothing is implied. This is least privilege by construction: a new project or a new area is invisible to a Member until you grant it.
What you can grant a Member
Two kinds of permission, each at View or Edit (Edit includes View):
- Projects. Either an all-projects default, or specific projects one at a time. A project’s level covers all of its surfaces — deployments, logs, caching, environment variables, database, files and settings. View lets someone read; Edit lets them deploy and change configuration. A Member only sees the projects they’ve been given.
- Organization areas. Data Workshop, Compute (jobs & queries), Domains, Billing, Usage & plan, API keys, Passkey (Canner Auth), Organization, and the Audit log — each grantable at View or Edit. Billing (payment methods, invoices, subscription) and Usage & plan (what you’re on, how much you use) are separate, so you can show usage without granting control over payment.
Managing users is an admin-only power; it isn’t something you can hand to a Member through a permission.
Inviting & accepting
Invite by email and choose their role and permissions up front. They get a link that expires in seven days. If they already have a Canner account they sign in and join; if not, they create one first. Either way they must accept while signed in as the invited email address — a forwarded link can’t be redeemed by someone else.
A person can belong to more than one organization. When they do, a switcher appears in the sidebar to choose which organization the dashboard is acting on.
Seats & billing
A seat is one user or one pending invitation. Free plans include unlimited seats. On a plan with a fixed number of included seats, inviting past that number adds a paid seat to your subscription automatically (prorated); removing a user frees it again. You’ll be told if an invite needs billing that isn’t set up yet.
API tokens & the CLI
An API token acts as the user who created it, in that user’s organization. It can never do more than that user can — a token’s reach is the user’s permissions and the token’s own scopes, whichever is narrower. Remove a user and their tokens for that organization stop working immediately.
What gets recorded
Invitations, acceptances, role and permission changes, and removals are all written to the audit log with who did it and when.