Diese Seite ist noch nicht übersetzt — sie wird auf Englisch angezeigt.

← Back to blog

Who can do what in your okokumo team

2026-11-02

engineeringsecurity

When you sign up, okokumo creates an organization and makes you its owner. An organization has exactly one owner. Anyone you invite after that joins as an admin or a member. This post lists what each of those roles can do and what happens at the edges: the owner, an expired invitation, a teammate who leaves. Every rule here is checked in the Go handler for the route, so it applies the same way in the dashboard, over curl, and through an AI assistant.

Updated 3 November 2026: the first version of this post said an admin could make anyone an owner, themselves included. That's no longer possible. Each organization now has one owner, nobody can grant the role, and ownership moves only through support. The sections on the owner and on admins below describe the new rules.

The matrix

Action Owner Admin Member
See members and pending invitations ✓ ✓ ✓
Invite admins and members, revoke invitations ✓ ✓ —
Switch people between admin and member, remove them ✓ ✓ —
Grant the owner role, change or remove the owner — — —
Rename the organization ✓ — —
Start a subscription, open the Stripe portal ✓ ✓ —
Create or revoke API keys ✓ ✓ —
Approve or disconnect apps (OAuth, MCP) ✓ ✓ —
Export the whole organization ✓ ✓ —
Export your own data ✓ ✓ ✓
Edit the status page, its components and domain ✓ ✓ —
Post, update or delete status-page incidents ✓ ✓ —
Run a check now, start or end maintenance ✓ ✓ —
Create, edit, pause, delete and import checks ✓ ✓ ✓
Create, edit, test and delete alert channels ✓ ✓ ✓

The empty row isn't a mistake. Nobody in the organization can hand out the owner role or take it away, the owner included. That goes through support, as described below.

Members can read everything in the list: the plan, the API key list (names and prefixes, never the keys), the status page and its incidents.

Note the last two rows. A member is not a read-only seat. Members can create, change and delete checks and alert channels, but they can't post anything to the public status page. The roles separate who runs the account from who does the monitoring work. They do not separate read from write. If you want someone to look but not touch, okokumo has no role for that today.

What a member actually sees

The Team page shows the role dropdown and the Remove button on every row except the owner's, to everyone. The server decides, and the page prints its answer. A member who tries to promote themselves gets:

HTTP/1.1 403 Forbidden

{"message":"only owners and admins manage team members"}

Each area has its own sentence, so the error says what was refused:

  • Inviting: only owners and admins invite team members
  • Billing: only owners and admins manage billing
  • API keys: Only owners and admins manage API keys
  • Connecting an app: Only owners and admins can connect apps
  • Organization export: only owners and admins export organization data
  • Status page: only owners and admins can manage the status page
  • Run now: only owners and admins can run a check

The same check runs no matter how the request arrives. An API key acts as the person who created it, with that person's role at the time of the request, because the membership is loaded again on every call. If an admin is demoted to member, their keys can no longer post incidents from the next request on. The MCP server sends each tool call through the same /v1 routes, and a test asserts that a member's assistant gets the same 403 on create_incident that curl gets.

Some routes don't accept an API key at all, whatever the role: team management, billing, API key management and both data exports require a signed-in browser session. A leaked key can't invite anyone or create another key.

One owner, and nobody can hand it on

The owner is the account that answers for the organization, so "who is the owner" has one answer. The database enforces it: a partial unique index on memberships allows one row per organization with the role owner. Two requests racing each other can't produce a second owner, whatever the application code does.

The Team routes refuse three things, whoever asks, the owner included. A role change to owner, or an invitation with the owner role, gets:

HTTP/1.1 403 Forbidden

{"message":"the owner role cannot be granted; contact support to transfer ownership"}

Changing the owner's own role gets the owner's role cannot be changed; contact support to transfer ownership, and removing the owner gets the owner cannot be removed; contact support to transfer ownership. In the dashboard, the owner's row shows an Owner badge instead of the dropdown and the Remove button, and the invitation form offers admin or member.

The team package's tests cover each rule: TestNobodyCanGrantOwnerByRoleChange, TestNobodyCanInviteAsOwner, TestNobodyCanDemoteTheOwner, TestNobodyCanRemoveTheOwner, and TestDatabaseRefusesSecondOwner for the index itself.

Transferring ownership

To hand the organization to someone else, email support@okokumo.com. The new owner has to be a member of the organization already, with a verified email. Support moves the role in one transaction. The previous owner becomes an admin, and the transfer is logged: from whom, to whom, and which of our staff ran it. Billing doesn't move, because the Stripe customer belongs to the organization, not to whoever owns it. The subscription and invoices carry on unchanged.

This is slower than a button, and we chose it on purpose. There is no request a signed-in session can make, hijacked or not, that gives the organization to someone else.

If your organization had more than one owner before this change, the earliest of them kept the role and the others became admins. Pending invitations to the owner role were deleted. Send a new admin or member invitation instead.

Admins run the team, not the owner

Admins can invite people as admin or member, switch anyone except the owner between those two roles, and remove admins and members. They can't touch the owner's membership in any way. Apart from that and the rename below, an admin can do everything the owner can: billing, API keys, connected apps, the organization export, the status page. So make someone an admin only if you trust them with those.

Leaving

There's no separate Leave organization button. You leave by being removed on the Team page. Admins can remove themselves. Members can't remove anyone, themselves included, so a member who wants out asks the owner or an admin.

The owner can't leave or step down from inside the product. Ask support to transfer ownership first. Once you're an admin, the new owner or another admin can remove you, or you can remove yourself.

Invitations

Inviting someone creates a token from 24 bytes of crypto/rand, hex-encoded to 48 characters. The database stores only its SHA-256 hash. The raw token lives in the link we email, /invite/<token>. The dashboard also shows that link once, right after you send the invitation, for when email doesn't arrive. We can't rebuild a link from what we store, and the organization export lists pending invitations without the hash.

When someone opens the link, the server hashes the token and looks for a row with that hash and an expires_at still in the future. The expiry is set to exactly seven days after the invitation was created, and the email says so. An unknown token and an expired one get the same answer:

HTTP/1.1 404 Not Found

{"message":"invalid or expired invitation"}

That's what production returned for a made-up token while we wrote this post.

Some other rules on that path:

  • One live link per address. Inviting the same email again deletes the earlier invitation in the same transaction, so the older link stops working. A unique index on organization and email backs this up.
  • Single use. Accepting creates the account and its membership with the invited role, then deletes the invitation, all in one transaction.
  • The inbox is the proof. The invitee chooses a password, at least 10 characters, and the account starts with its email already verified, because following the link proved they control that address.
  • One organization per account. An account belongs to exactly one organization for now. Inviting an address that already has an okokumo account fails straight away with 409 an account with this email already exists, so you don't send a link that could never be accepted.

Revoking an invitation from the Team page deletes the row, and the link then gets the same 404.

Removing someone

Removing a member deletes their membership. Any apps they connected to the organization through OAuth are revoked at the same time, not the next time those apps fail a lookup. API keys they created stop working too: a key authenticates as its creator's membership in its own organization, and once that membership is gone the request gets 401 No organization membership. The rows still appear in the key list, so revoke them as well to keep the list accurate.

Renaming is owner-only

Apart from the owner rules above, PUT /v1/organization is the one action admins can't take:

HTTP/1.1 403 Forbidden

{"message":"only the owner can rename the organization"}

The name is trimmed, must not be empty, and can be up to 100 characters. It appears in the header of every teammate's checks page, in the subject of invitation emails, on the page an invitee sees ("Join Acme") and on the consent screen when someone connects an app ("Connect an app to Acme?"). If the organization has a subscription, it's also printed on Stripe invoices as an Organisation line, next to the legal name entered at checkout. Renaming doesn't change that legal name, and invoices already issued keep the old organization name. Because the name shows up on invoices, we treat it as an owner decision. Nothing else keys off the name.

The membership and invitation rules live in the API's team package, about 440 lines plus tests. You'll find the roles under Account → Team in the dashboard. If a rule here gets in your way, or you need a role this model doesn't have, tell us.