kral Documentation
Sign in
Dashboard

Team and organization

A team puts several people on one bill. Members chat and use the API like any other account; the costs draw from a shared credit pot that one person, the owner, funds and controls.

How the shared pot works

The owner's credit is the team's credit: the monthly team plan refill plus any top-ups the owner makes. Members do not need their own subscription or payment method, and their dashboard shows a team card with their personal budget instead of billing controls.

Roles

  • Owner: pays, owns the credit pot, and manages everything including the subscription.
  • Admin: manages members and settings, no access to billing.
  • Member: uses the chat and API against the shared pot.

One account belongs to at most one team.

Creating a team

Click Create a team on the dashboard and subscribe to a team plan. You become the owner, and the organization pages (Overview, Members, Usage, Settings) appear in your dashboard. For assisted onboarding of a larger company, including enterprise single sign-on, contact us.

Inviting members

Under Members, invite people by email. The invite arrives as a link: existing accounts join the team when accepting, and people without an account create one directly from the invite. Admins and owners can change roles after joining.

Budgets

Each member can have a monthly budget, a cap on what they may spend from the shared pot per month. Without a budget, a member is limited only by the pot itself. When a member hits their budget, their requests pause until the month resets or the cap is raised; the rest of the team is unaffected.

Suspending and removing

Suspending a member keeps their seat and history but blocks their requests until reactivated, useful for leave or off-boarding in progress. Removing them frees the seat entirely.

Seeing what the team spends

The organization's Usage page breaks consumption down per member: requests, tokens, and cost. Combined with budgets, this answers both "where does the money go" and "who needs a higher cap".

Support

Team owners and admins can raise support tickets on behalf of the organization, so billing questions stay visible to the people managing the plan.