R2.3 · Free remedy

The agent runs on an account with broad access

an agent connected through an admin login can do everything that login can — and so can anyone who hijacks the agent.

Why underwriters ask about it

an agent connected through an admin login can do everything that login can — and so can anyone who hijacks the agent.

How to fix it

  1. Create a separate account for each agent with only the permissions its job needs — never the owner's login, never admin.
  2. Remove access it doesn't use (if the booking bot doesn't need payment history, take it away).
  3. When a staff member leaves, treat agent credentials like theirs: rotate them.

Evidence to keep

a note per agent of which account it uses and what that account can reach.