Devora Cloud · Blog
When to revoke the AI token
Devora Cloud · Reviewed on
Revoke the token when publishing is done, when it leaked or when you switch AIs. Access drops immediately.
The token is the account key in the hands of the conversation. Conversation over, key left on the table, is a risk. Revoke is the button next to the token, in the list.
Generate another when you publish again. The new text is a new value. The old one stops opening the API immediately.
Also revoke if
The build log showed the token. Someone pasted the text into a group. You left the AI and do not remember whether the thread kept the key. When in doubt, revoke and generate again in a new conversation.
What this does not revoke
The project, the database and S3 stay. Revoking does not delete the site. It deletes the access of that credential.
Frequently asked questions
Is the developer key the same thing?
No. It is also revoked from the same list, but it was made for scripts and CI, without the text the AI pastes.