Account

# Organizations and team

Create organizations, invite members, and manage roles.

Signing up creates only your account. Create an organization from the dashboard, or join one by opening an invite link. You can belong to several and switch between them from the organization menu.

## Slugs

Each organization has a **slug**, derived from its name when it's created (`Acme Inc` becomes `acme-inc`, with a short suffix if that's taken). The slug is in every read URL (`/v1/acme-inc/mobile-flags`) and in the dashboard address, so it **never changes**. Renaming the organization changes only its name.

## Roles

| Role | Can |
| --- | --- |
| Owner | Everything, including billing, deleting the organization and handing it to someone else. Every organization has exactly one. |
| Administrator | Everything except billing and deleting the organization: production, API keys, members and invites, roles, the organization's name, the audit log and export. Administrators can't change or remove the owner. |
| Member | Work in development and staging: create bins, publish, promote between them, roll back, copy production down. |

Only administrators change **production**: publishing to it, promoting to it, rolling it back, unpublishing or deleting it, deleting a bin that has it, changing a bin's visibility (which decides who can read production), and changing the schema of a bin that has a production environment (which decides what can be published to it). A member who tries gets `403 production_admin_only`, in the dashboard and the API alike. The usual flow is that members publish to staging, and an administrator reviews the diff and promotes.

Whoever creates an organization owns it. The owner can't be removed, demoted or leave. To step back, the owner opens **Settings → Team** and chooses **Make owner** on another member: that person becomes the owner and the previous owner an administrator, in one step. Only the owner can do this.

## Invites

Administrators invite people by email under **Settings → Team**. Each invite counts as a seat until it's accepted, revoked or expires. If email isn't delivered, the dashboard shows the invite link to share yourself.

## Removing a member

Removing a member (or a member leaving) ends their access at once and revokes the API keys they created. Their published versions stay in history.

## Over the API

| Request | Does |
| --- | --- |
| `POST /v1/organizations` | Create an organization you administer: `{"name": "Acme Inc"}`. |
| `PATCH /v1/organizations/:id` | Rename it: `{"name"}`. The slug can't be changed. |
| `GET /v1/organizations` | The organizations you belong to, with your role in each. |

A dashboard session acts in the organization named by the `X-Hotcfg-Organization` header (slug or id). API keys belong to one organization.

Last updated 10 November 2026
