Bot Permission Containment Review (QA)
A checklist with 7 steps: Inventory every bot, agent, and browser worker touching a client account before the review starts.
By InnovaAI ResearchPublished
What are the steps?
Bot Permission Containment Review (QA)
- 01
Inventory every bot, agent, and browser worker touching a client account before the review starts
List each automation by name, owner, and the systems it authenticates into. Warmwind-style visual workers and prompt-built scrapers like BrowserAct both need to appear on the same register, since neither leaves an obvious code trail.
- 02
Assign each automation a single named owner inside the agency
Unowned bots are the ones that keep running after a retainer ends. One name per bot, recorded in the delivery tracker, with a named backup.
- 03
Strip credentials down to the minimum scope the task actually needs
Read-only where the bot only reads. No admin tokens for a workflow that posts a single update. Reissue keys rather than editing inherited permissions.
- 04
Test each bot against a sandbox copy of the client environment
Confirm the automation fails closed when a selector breaks or an API returns an error, rather than improvising an alternate path through the UI.
- 05
Log every outbound action the bot takes for a full week
Capture destination, payload size, and timestamp. Review the log against the stated task scope and flag any call the client did not authorize in writing.
- 06
Set a kill switch the account manager can reach without engineering help
Document the exact toggle, who holds it, and the response window. A bot that cannot be stopped in under five minutes is a retainer risk, not an asset.
- 07
Re-run the review on a fixed cadence and after any platform change
Quarterly at minimum, plus immediately after a vendor ships a major release. Enterprise suites such as Automation Anywhere change agent behavior between versions.