Panel keys
A panel key is what lets your server's agent prove it's allowed to report into the panel. Each key looks like `gm_live_xxxx`, belongs to exactly one server, and does one job: it authenticates the agent. It does not grant panel login, team access, or anything else.
What a key is scoped to
Keys are per-server. A key issued for one server only works for that server. If you run three servers, you have three separate keys, and a key from one server is useless on another.
The key authenticates the outbound agent connection and nothing more. It is not a session token for the web panel and it carries no team role. Who can see or change a server inside the panel is controlled by team roles, which are independent of the panel key.
How keys are stored
The panel stores only a hash of your key, never the key itself. You see the full value exactly once, at the moment it is created. After that the panel can show you which key exists and let you revoke or rotate it, but it cannot show you the value again.
Note: Because the key is shown once, copy it straight into your agent config when you create it. If you lose it, there is no recovery step. Rotate the key on the Connection card to get a new one.
Rotating and revoking
- 1Open the server and go to the Connection card.
- 2Choose rotate to generate a new key, or revoke to disable the current one.
- 3Copy the new key value while it is shown (rotate only).
- 4Paste it into your agent config and restart the server once.
Rotating disconnects the old agent immediately. The previous key stops working the moment you rotate, so the server goes offline in the panel until the agent restarts with the new key. Plan the rotation for a moment when a single restart is acceptable.