Fixes / Security
Deleted a Bot, but its access is still there
Deleting a Bot doesn't remove sessions, files or connector authorisations from the shared computer. What to revoke, where, and in what order.
Short answerBot deletion removes the Bot, not its footprint. Revoke from the source: sign out sessions on the shared computer, delete the Bot's tokens in each tool, remove its connector authorisation, delete its files, and only then delete the Bot account itself.
What actually happens on delete
The Bot's chat and job description go away. The cloud computer, its browser profile, files and connector authorisations are account-level and stay. If the Bot had used your session, that session is still signed in.
Offboarding order
- Pause all its routines.
- In each tool, revoke the Bot's tokens and deactivate its user.
- Under Settings → Plugins, remove any connector that only this Bot used, or re-authorise shared ones as a different Bot user.
- On the shared computer, sign out of anything the Bot signed into; delete its working folder.
- Delete the Bot.
- Delete the Bot's email account, or convert it to a group so nothing important bounces.
Same order as offboarding a contractor, which is the right way to think about it.
Verified 28 Aug 2026 · Facts about Grok Bot change during beta. See changelog.