A surprising number of automation pilots start with someone pasting an owner password into a chat. Access setup is one of the most practical tests of how to choose an AI automation agency that respects your systems: watch what they ask for.
What a careful agency asks for
- Its own user accounts, never shared logins. Every action is then traceable to them.
- The smallest role that works. Read access first; write access only for the objects the pilot touches.
- Scoped API keys created for the project, named after it, and easy to revoke.
- A test or sandbox environment where the tool offers one, or a separate test phone number for messaging.
- A list of every credential they hold, kept by you.
A simple access register
system | account | scope | created | revoke by
crm | agency-pilot | contacts, deals | (date) | end of pilot
whatsapp | test number only | send, receive | (date) | end of pilot
email | none (forwarding) | n/a | n/a | n/a
Keep it in your own drive, not theirs.
Red flags
- Asking for owner or super-admin rights "to save time".
- Keys created under a builder's personal account.
- No answer to "how do we remove your access?"
Offboarding test
Before the pilot ends, revoke one key on purpose and check that the workflow fails safely and someone is alerted. If revoking access breaks things silently, you have learned something important.
For help picking the right pilot workflow, read our audit guide; our own first audit takes 72 hours.
Top comments (0)