Organizations

Organizations let you share API keys with collaborators under a single owner. Usage on an org's keys counts against the org owner's plan, so a team can run production traffic through keys that outlive any one member.

Where to Find It

Sign in to the dashboard and open Organizations in the sidebar. Every org you belong to appears as a row in a sortable table with its name, your role, member count, key count, and creation date.

Creating an Organization

Click New Organization, enter a name, and confirm. You become the org's owner. The slug is auto-derived from the name.

Roles

Owners and admins see every key owned by the organization on the API Keys page.

Renaming an Organization

Click Edit on any row where you're an owner or admin. Rename it, save, and every key display picks up the new name.

Assigning Keys to an Organization

There are two ways to place a key under an organization:

1. On creation: the Create Key dialog on the API Keys page shows an Owner picker whenever you belong to an org. Pick the org instead of Personal.
2. Transfer an existing key: the Transfer action on any key you own moves it into an org (or back out) without regenerating the secret. Metrics and Activity history follow the key.

Billing Attribution

Every request made with an org-owned key is billed to the org owner, not the person who fired the request. That's why moving a key into an org matters: it changes who the usage counts against for plan limits and invoices.

If ownership of an organization needs to change, contact support.

Teams

Team-level sharing (splitting an org into smaller groups with per-key permissions) is not currently surfaced in the dashboard. Organization owners and admins see every org-owned key.

Related

• Managing API Keys: Create, transfer, and manage keys within an organization
• Billing & Subscriptions: How the org owner's plan covers org-key usage
• Dashboard Overview: All dashboard sections