/admin/onboard — the guided
walkthrough, and the place tokens live.
Create a token
1
Switch to Create new token
Step 1 of the walkthrough is Get an enrollment token.
2
Name it
Give it a name, and a description if that helps. Names matter later: the
list shows who issued each token and when it last enrolled a machine.
3
Press Create token
The token is revealed exactly once, at that moment — together with the
install command to paste.
Hold as many as you find useful
One per datacenter, one per bootstrap script, one for a contractor you revoke afterwards. Tokens are reusable — the same line rolls out a whole rack. They belong to your operator, not to your seat. Every admin on your team sees the same list, with each token’s name, who issued it, and when it last enrolled a machine — and can revoke any of them.Revoking
Revoking deletes the token. It stops enrolling immediately.Every server already installed with it keeps running. Each machine holds its
own credential rather than a copy of your token, so revocation affects future
enrollments only.
Where enrolled servers land
Every server enrolled with one of your tokens joins your operator’s capacity pool — yours alone, never visible to customers, and never to another operator. From there:- Your customers rent whole nodes out of your pool from their own console.
- You can reassign any node manually at any time.