Account
The Account section manages your personal CMDOP identity: profile, two-factor enrollment, API tokens, OAuth providers, and support tickets. It is independent of any fleet — your account survives fleet churn.
Primary surface is desktop and CLI for actual operations. Account management lives here because it is identity work, not operational work. The desktop app and CLI honor the credentials you set up here.
Sections at a glance
Identity, email, linked fleets, notifications.
SecurityPassword, 2FA, active sessions, hardware keys.
API tokensPersonal and fleet tokens for SDK, CLI, and integrations.
OAuth appsLinked sign-in providers and authorized third-party apps.
SupportTickets, status page, security disclosure.
How account vs fleet works
- Your account holds personal credentials, notification preferences, and OAuth links.
- A fleet holds machines, members, billing.
- One account can belong to many fleets. Switching fleets does not change your account.
Where this data lives
Your account is stored at the account level, independent of any fleet — it follows you across every fleet you belong to.
Cmdop