Skip to content

Keys ​

A key goes in your product's builds and tells ALIAS which product a report is for. It isn't a secret: anyone with a build can find it. So ALIAS limits what a copied key can do, and lets you cut one off at once. Admin → Keys lists each product's keys, with when each was issued and last used.

Issuing a key ​

Issue key, and name it after the build or platform it goes in (web, steam, ios). A product can have as many as it needs, so one build can be cut off without the rest. The key is shown once: copy it before you close the dialog. Only a hash of it is kept.

When a key leaks ​

DoesUndone with
Quarantinethe key keeps working, at a twentieth of the product's limits, and its reports are marked on the desk. Old builds keep reaching support while the leak can't do muchRelease
Revokethe key stops at once. You can add what the app tells its usersRestore

Quarantining and revoking need keys.revoke; issuing, releasing and restoring need keys.issue. Every change is in the log.