Documentation

Organizations and groups

An organization lets a whole company share one prepaid balance while keeping each team's spending — and each person's keys — separate and accountable.

How an account is shaped

An organization holds one prepaid balance and any number of groups, up to a hundred. People belong to a group, and keys belong to people. A group can be given a spending limit; the balance itself belongs to the organization.

Organization            one prepaid balance
└── Group               a spending limit of its own
    └── Member          a person who signs in
        └── API key     what your code actually sends

Groups exist so one team cannot quietly spend the whole company's credit. A group limit caps how much of the shared balance the keys counted toward that group may use — it is a ceiling, not an allowance set aside in advance.

Roles

What each role in an organization may do
Role	What they can do
Organization admin	Everything below, across every group: create groups, invite members, set group limits, issue and revoke keys, read the balance and top it up.
Group admin	Within their own group only: invite members, set that group's limit, and issue or revoke keys for themselves or any of its members. They cannot act on another group.
Member	Collect a key an admin granted them, use it, and revoke it. They cannot issue keys, change a budget, or see anyone else's keys.

Whoever sets the organization up becomes its organization admin. That role is not handed out by invitation — everyone invited afterwards joins as a group admin or a member.

Inviting colleagues

An organization admin or a group admin invites people from the group's page in the portal: enter a work email, pick group_admin or member, and they are invited. They then sign in exactly as described in Getting started.

One account per email address

An address that already has a Kakehashi account — in your organization or anyone else's — cannot be invited again. Ask the person to sign in with the account they already have.

Keys in an organization

Granting a key to a member

Members cannot issue their own keys, and an admin cannot issue a key and hand it over, because a key's value is shown once to whoever creates it. So the portal splits the act in two: an admin grants a key — naming the recipient, the label and any cap — and the member collects it from their own dashboard.

The key is created at the moment of collection, in the member's own session. Nobody else, including the admin who granted it, ever sees the value.

A grant can be cancelled while it is still uncollected. Once collected, revoke the key instead.
A grant can only be collected by the person it names, and only while they are still a member of the organization.

Counting a key toward another group

An organization admin issuing a key for someone else can choose which group the key's spending counts toward. That lets one person hold two keys billed to two different teams, without changing which group they themselves belong to.

Decided at issue time only

A key cannot be moved to a different group afterwards. If a key is counting against the wrong group, revoke it and issue a replacement.

Budgets and limits

Key budget — an optional cap on one key. In an organization, only an admin of that key's group can change it, even when the key is the member's own.
Group limit — a cap on everything counted toward one group. It can renew daily, weekly or monthly, or not renew at all.
Organization balance — the prepaid credit itself. It has no settable ceiling, because the balance is the money you paid. To limit spending, use group limits.

Deleting a group

An organization admin can delete any group other than their own. This is permanent and takes the group's keys with it: those keys stop working immediately, and the group's members are removed from it.

There is no undo

Deleting a group cannot be reversed, and the keys it held cannot be restored. The confirmation dialog spells out what will go — read it rather than clicking through it.

Who sees what

Every member of an organization can see the list of groups and each group's spending against its limit. Only an organization admin can read the prepaid balance. Nobody can see, use or revoke a key belonging to someone whose group they do not administer — enforced on the server for every request, not merely hidden in the interface.