Organizations
A Cmdop organization is a billing and membership boundary in the account console: it holds your plan and the people on it. It is not a fleet, and it grants nobody execution rights on any computer — each machine’s own permission policy decides that. Come here to work out which control lives where.
An organization is a billing and membership boundary in the account console . It is where your plan lives and who is on it — see Billing.
An organization is not a fleet. A fleet is the set of machines under one relay, and what happens on those machines is decided by each machine’s own permission policy, not by your organization role.
Which controls are where
| Concern | Where |
|---|---|
| Plan, payment, entitlements | Account console → Billing |
| Organization members | Account console |
| Organization API keys | API keys |
| Which machines exist and who can reach them | The relay — web console → Server |
| What may run on a machine | That machine’s permission policy — Permissions |
| Who can attach to a machine remotely | The relay admin password and the machine’s connection PIN — Security |
The split matters when something is refused: check the machine’s permission audit before you look at anyone’s organization role.
Common questions
What is a Cmdop organization?
A Cmdop organization is the account-console boundary for members, plan, billing, and organization API keys.
Is a Cmdop organization the same as a fleet?
No. A fleet is the set of machines under one relay. An organization is an account, billing, and membership boundary.
Does an organization role grant machine execution rights?
No. Machine execution is governed by relay credentials and the machine’s own permission policy.
Cmdop