Create an organization, invite team members, and control who can access which API keys and spending data.
Not yet available. Organization management is tracked to be built — today, use Workspaces: create workspaces, switch between them, and add or remove members from the dashboard.
Workspaces are the live multi-user surface. From the dashboard you can:
Workspace membership is flat — every member has the same access. There is no roles matrix, per-member key assignment, or per-member spending limit yet; those belong to the intended organization design below.
The following describes how organization management is planned to work. None of it is live yet.
Roles. Members would carry one of four roles:
| Role | Permissions |
|---|---|
owner | Full access — billing, keys, members, analytics |
admin | Keys + analytics; cannot add/remove other admins or access billing |
developer | Access to assigned keys and their own usage analytics only |
billing | Billing and analytics read-only; cannot create keys or invite members |
Key assignment. developer members would see no keys by default; an owner or admin would assign specific keys, granting API access and per-key analytics without ever exposing the raw key value.
Per-member spending limits. A monthly DA cap per developer to prevent runaway spend.
Shared billing. All members would draw from the organization's single DA balance, with per-member cost attribution in analytics.
Until organizations ship, attribute spend by giving each member (or each app) its own API key. The activity export filters by key_id, model, from, and to — one key per member gives you clean per-member cost breakdowns, and the analytics API covers daily rollups.