Managing Your Organization

Organizations are the top level of the platform: every project, environment, and resource lives inside one. This page covers day-to-day organization administration — settings, members, roles, ownership, and deletion.

Organization settings live in the dashboard under Organization Settings, split into seven tabs: General, Members, Groups, Variables, Secrets, Integrations, and Usage.

Your personal organization

When you join the platform (by accepting an invitation), a personal organization is created for you automatically — one per user. It works like any other organization, with two differences: a personal organization cannot be deleted on its own (only by deleting your account), and its ownership cannot be transferred to anyone else. Its General tab has no Danger Zone.

Use your personal organization for experiments, and create a separate organization for anything a team works on together.

Creating an organization

In the dashboard, open Create Organization and fill in:

Organization Name — the display name, editable later. Organization names must be unique on the platform (case-insensitive).
URL Slug — 2–50 lowercase letters, digits and hyphens, starting with a letter and not ending in a hyphen; used in URLs (for example /orgs/acme). It’s generated from the name as you type and can be edited before you create the org, but not afterwards.
Description — optional.

You become the organization’s owner. An account can create organizations while it owns fewer than three, not counting its personal one.

The CLI has an equivalent under paas orgs:

paas orgs list          # organizations you belong to
paas orgs info -o acme  # details for one organization
paas orgs create --help # see the create options
paas orgs update acme --name "Acme Inc"
paas orgs transfer acme --to new-owner@example.com
paas orgs delete acme --confirm acme

paas orgs set-default sets the organization the CLI falls back to when you don’t pass -o and you’re not inside a repository whose d2o (or older paas) git remote supplies one, and --json on any of these prints the raw API response for scripting.

General settings

The General tab lets you change the organization’s name and description. Edit the fields and click Save Changes.

Members and roles

The Members tab lists everyone in the organization with their role. Each member holds one of three roles:

Role	What it can do
Owner	Full control, including deleting the organization and transferring ownership. Every organization has exactly one owner.
Admin	Manage members, groups, and projects.
Member	Access only through the groups they belong to — see Groups & Project Permissions.

Owners and admins see an Invite Member button; new people join by email invitation — admins can invite Members, and only the owner can invite someone as an Admin. Pending invitations appear below the member list, where they can be revoked. Invitations are covered in detail in Inviting People.

Changing a member’s role

As the owner, each member row (other than your own) shows a role dropdown — switch it between Member and Admin and the change applies immediately. Other members see role badges only.

Removing a member

The owner can click Remove on a member row. The person loses access to the organization and its projects; you can re-invite them later. The owner cannot be removed — transfer ownership first.

Transferring ownership

An organization always has exactly one owner, and only the owner can hand that role to someone else. The new owner must already be a member; if necessary, invite them and wait for them to accept first. Personal organizations cannot be transferred.

The transfer takes effect immediately. The previous owner becomes an Admin, and all projects, environments, and resources stay in the organization.

In the dashboard

Open Organization Settings → General and find Transfer ownership in the Danger Zone.
Choose an existing member from New owner. The current owner is excluded.
Click Transfer ownership and review the recipient and role change.
Type the organization’s display name exactly as shown, then confirm the transfer.

Your role and the available organization controls update after the transfer succeeds.

With the CLI

Use the recipient’s email address or user UUID:

paas orgs transfer acme --to new-owner@example.com
paas orgs transfer acme --to 00000000-0000-0000-0000-000000000002

The organization slug is required explicitly. Email matching is case-insensitive and only searches existing organization members. A UUID must be the member’s user ID, not their membership record ID.

The CLI shows the recipient and role change, then asks you to type the organization’s slug. For scripts, provide the matching --confirm value; a non-interactive command without it is refused:

paas orgs transfer acme --to new-owner@example.com --confirm acme --json

--json prints the updated organization returned by the API. See the CLI command reference for the full syntax.

Through the API

The same operation is available at POST /api/v1/organizations/<org>/transfer with {"new_owner_id": "<user_id>"}. Get the recipient’s user_id from GET /api/v1/organizations/<org>/members.

Deleting an organization

Only the owner can delete an organization, and personal organizations cannot be deleted on their own.

In the General tab, the Danger Zone section holds the Delete Organization button. The confirmation dialog requires typing the organization’s name, because deletion is permanent: it removes the organization and every project, environment, and resource it contains. There is no undo — make sure you have copies of anything you need before confirming: application data, configuration, and the secret values you originally set (secret values cannot be read back from the platform).

Organization variables

The Variables tab holds plain environment variables that every app in the organization inherits. An environment or an app can override any of them by setting the same key. Owners and Admins can change them; every member can read them. See Organization and environment variables.

a build fails (with a View build log link);
a deployment fails, is rolled back, or its rollback fails;
monthly bandwidth crosses 80%, 95% and 100% of the allocation;
resources are blocked, or restored, for the monthly transfer allocation;
a domain is released to another organization.

These emails are sent only if your installation has email configured.

Next steps

Inviting People — organization and project invitations end to end.
Groups & Project Permissions — give members access to specific projects.
Access Control — how roles, groups, and capabilities fit together.
Plans, Limits & Usage — what the Usage tab is telling you.

d2o PaaSdocs