Creator key management
Issue, inspect, revoke and reset managed project keys.
Open Dashboard → project → Keys for managed credentials. The summary separates Active, Unused, Expired and Revoked keys.
- Generate one or more manual keys for the project, with a custom lifetime from 1 hour to 1 year.
- Copy plaintext when a manual key is first issued. Stored history shows only a masked value.
- Check whether a key is Bound or Unbound and when it was last used.
- Revoke a credential immediately.
- Reset the device on an active bound key. Its expiration does not change; the next compatible device to validate it becomes bound.
Public acquisition uses the project's configured duration, which can be any duration from 1 hour to 1 year. Creator-issued keys can use that default or their own duration in the same range. A creator-issued unbound key does not occupy a device's public-key slot until it is bound.
- Add a private note when generating manual keys, and revoke all active keys at once.
- Turn on Only the owner can generate keys. While it is on, players cannot get new public keys; existing keys and keys generated manually or through an owner-authorized API token keep working.
Bulk, incident and integration controls are described in Project controls and activity. Keys can also be generated, listed and revoked from your own tooling with the creator API.