This guide covers the lifecycle of an organization from the inside: creating one, adding people, granting owner status, and transferring ownership when needed. For the concept of what an organization is, see Organizations.

Creating an organization

Any signed-in user can create an organization. Open the user menu → Organizations → + New organization. Provide:

  • Name — appears everywhere the organization is referenced.
  • Short code (if asked) — used in URLs and references.

You become the first owner automatically. The organization starts with no other members, no roles, no tenants, and no schemas.

Adding members

From the organization page → Members tab:

  1. Click + Add member.
  2. Enter the user's email or pick from existing platform users.
  3. Choose whether they join as owner or member.
  4. If member, optionally pick the roles they should start with.
  5. Save.

The user appears in their own Organizations list the next time they sign in.

Owners vs members

Owner Member
Manage members yes no
Define and assign roles yes no
Manage org-owned tenants and schemas full only what their roles grant
Be removed only by another owner by any owner
Need explicit roles no yes

An organization can have several owners — useful when more than one person needs full administrative control.

Promoting a member to owner

From the member's row in the Members tab, click Make owner. The user gains full implicit permissions on every org-owned resource immediately. Demoting an owner back to member is the reverse action.

A safety rule: an organization must always have at least one owner. The last owner cannot demote themselves until another owner takes over.

Removing a member

From the member's row, click Remove. The user loses access to every tenant the org owns and every role they had. Data they created stays — only their access goes.

If you remove someone who created instances, those instances keep createdBy = <that user> for audit. To replace a user (someone leaves the team), prefer adding the replacement first and then removing the old account, rather than reusing roles by name alone.

Transferring ownership of a resource

Tenants and schemas can move between users and organizations:

  • User → Organization — the original user transfers their resource to the org. The user can keep being a member.
  • Organization → another organization — done by an owner of the source org, with consent of an owner of the target.
  • Organization → User — convert an org-owned resource back into a personal one.

The action lives under each resource's settings (look for Change owner or Transfer ownership). The acting user must have the right to manage the resource.

Leaving or deleting an organization

  • Leave — a member can leave at any time from their own profile. They lose access immediately.
  • Delete — an owner can delete the organization, but only when it owns no tenants and no schemas. Transfer or delete the contained resources first.