Skip to main content
More seats at your operator come from NeoChamber: ask for another operator invite naming your datacenter, and whoever redeems it at /register becomes an admin alongside you. Codes are single-use, valid 14 days, and shown exactly once.

​
Why invites are scoped

An invite names the operator it joins. A colleague therefore never lands in a different datacenter, and never accidentally creates one of their own.

​
What an operator admin can do

Inside your datacenter, an operator account is root. Anyone you add sees every one of your tenants’ machines and telemetry and your whole capacity pool, and can reassign nodes, issue and revoke the operator’s enrollment tokens (yours included), and create tenants.There is no narrower role within an operator yet, so keep your own list short.
What they cannot see, ever, is another operator. That boundary is enforced on the server from the session and proven by an automated cross-operator test on every release — see Isolation.

​
Removing someone

Removing a teammate’s account happens in a deliberate order:
  1. Their sessions are killed first.
  2. Then the account.
  3. Then every invite and reset code it handed out is revoked.
Their enrollment tokens are not revoked with them. Tokens belong to the operator rather than to a seat, so revoke those separately from the token list on /admin/onboard — it names who issued each one.Either way, the servers they installed keep running: each node holds its own credential, not theirs.

​
Traceability

Every invite minted and redeemed is recorded. See what is audited for the precise scope of the audit log — it is narrower than “everything”, and the console says so too.