Organizations
The organization is the top-level account boundary. Users, billing, projects, and environments all belong to an organization, and almost everything you do in the app happens in the context of one.
What an organization owns
An organization groups together the people who work on your rules and the resources they share. A single account can belong to several organizations — for example, a personal sandbox and a company workspace — and each one keeps its own data completely separate. Every organization owns:
- Members — the users who can sign in to the organization, each with a role.
- A plan and billing state — the subscription tier, credit balance, and payment method. See Plans & Tiers and Credits & Billing.
- Projects — the rule sets and authoring work your team builds.
- Environments — the targets where rules execute. See Environments.
Membership and roles
Members are identified by email address and carry a role that determines what they can do. There are three roles:
| Role | Typical capabilities |
|---|---|
| Owner | Full control, including members, plan, billing, and credits. Held by whoever created the organization until it is handed on. Exactly one member holds it at a time. |
| Admin | Administrative access: manage members, plan and subscription, credit purchases, payment methods, and environments. |
| Member | Works within the organization’s projects and environments without billing or administrative rights. |
Billing-sensitive actions — buying credits, saving a payment method, and changing auto-recharge — are restricted to administrators (Owner and Admin). Members can build and run rules but cannot change what the organization is charged.
Invitations that have not been taken up
You add a member by entering their email address, which means a row can exist before the person behind it does. A member who has been invited but has not signed in yet is marked Pending in the member list. They hold their role from the moment they first sign in; until then there is no account behind the row, which is why a few things — ownership of the organization, for one — cannot be handed to them.
Members whose accounts have been removed
When somebody’s account is erased, their name and email address go with it, but everything they did stays on the record. Their past work reads as Deleted user wherever an author, approver, or run initiator is shown, including the audit log. History is never rewritten to remove them.
Transferring ownership
Ownership can move to another member from the organization’s settings page. Only the current owner sees the option, and only on an organization that already exists.
- Open the organization for editing and find Transfer ownership under the member list.
- Pick the member who should become the owner. Only members who have actually signed in are offered — an invitation nobody has taken up has no account behind it to own anything.
- Confirm. The change takes effect immediately.
You stay in the organization as an Admin afterwards, so you keep administrative access. What you give up is what only an owner can do: transferring ownership again, and deleting the organization.
An organization with no owner has nobody who can administer it, so an account cannot be erased while it still owns one. If you are handing over your work, move ownership of every organization you own first.
Switching organizations
After you sign in, you choose which organization to work in. If you belong to exactly one, the app selects it automatically; otherwise you pick from a list. Selecting an organization scopes your session to it and applies the role you hold there — see Authentication for how signing in works. You can switch organizations at any time, create a new one, or edit an organization you administer.
When you create an organization you can also opt to add an example project — a starter project, enabled by default, that gives you working rules to explore instead of an empty workspace. Clear the option if you would rather start from scratch.
Your active organization scopes everything you see: projects, environments, usage, and billing. Switching organizations changes that context entirely — you are never looking at two organizations’ data at once.
The organization dashboard
The organization dashboard is the home view for the active organization. From here administrators reach the things the organization owns: its members, its current plan and usage against the monthly run limit, its credit balance and billing settings, and its environments. It is the starting point for upgrading a plan, topping up credits, or provisioning a new environment.
Administrators on higher tiers also reach the organization’s governance and security screens from here — audit history, access policy, custom roles, machine API keys, deployment pipelines, and backups. See Enterprise & Governance for the full set.