Organizations

Everything an owner or admin does after the organization exists: who is in it, how they get in, what authenticates on its behalf, and where its files live. Teams and organizations covers the context itself, the roles, and the shared credits and usage every member can read.

Members #

Any member may read the member list. As an owner or admin you can change a member's role or their monthly credit budget, and remove them. A member can also remove themselves, which is how you leave an organization.

The owner is the exception: transfer ownership first, with POST /organizations/{id}/transfer-ownership, and the previous owner becomes an admin. Removing someone also stops their organization API keys from authenticating, so revoking access is one action rather than two.

Invites #

An invite is addressed to one email address and lasts seven days. Its plaintext token and URL are returned once, when the invite is created or resent, so capture them from that response; resending rotates the token and extends the expiry. The signed-in account accepting an invite has to match the address it was sent to.

Pending invites that consume a seat count against the seat limit before they are accepted, so an organization cannot oversubscribe itself by inviting. Viewer invites do not consume a seat.

Verified domains #

Claiming a domain proves you control the addresses in it, which is what lets colleagues join without an individual invite.

1. POST /organizations/{id}/domains returns a TXT record to publish at _nolgia.<domain>.
2. Publish it in your DNS.
3. POST /organizations/{id}/domains/{domain}/verify reads DNS and marks the domain verified.

A missing or mismatched record answers 409, and so does a domain another organization has already verified. Once verified, PATCH /organizations/{id}/domains/{domain} turns on auto-join, so a new account with an address in that domain lands in the organization, and SSO enforcement, which requires a verified domain and an enterprise organization.

Organization API keys #

An organization API key authenticates as the organization rather than as a person: it is bound to the organization it was created for and never follows anyone's active context. It carries its creator's current role, and it stops working when their membership ends.

The plaintext token is returned once, at creation. Store it where your application reads its secrets, and revoke it with DELETE /organizations/{id}/api-keys/{key_id} rather than rotating in place. Get your API key has the token format and how it differs from a personal one.

Bring your own storage #

On an enterprise plan, an organization can keep its media in its own S3-compatible bucket. Create the connection, then POST /organizations/{id}/storage-connections/{connection_id}/test and read the status it returns before trusting it: a connection that cannot be probed is a configuration to fix, not something to discover at the first upload.

Two directions are available once it works. import brings objects that are already in the bucket into the organization's Library, and backfill queues every ready organization asset for mirroring into the bucket. With mirroring enabled, new assets are copied as they become ready.

The audit trail #

Every administrative action above is recorded. GET /organizations/{id}/audit-events lists them newest first, filtered by action or actor, and enterprise organizations can download the whole trail as CSV. See Teams and organizations.