Connected devices
Every machine you authorize with zevron login appears as a session — device, location, and last active. Revoke any of them to cut off access immediately.
API tokens
For CI, create a long-lived API token instead of an interactive login. Tokens are shown once at creation — copy it then, because it can't be retrieved later — and can be revoked at any time.
$ zevron login --token $ZEVRON_TOKENNote
Treat a token like a password. If one leaks, revoke it — every build it ran stays on record under its name.
Manage them
Devices and tokens live under CLI sessions in your account.