Connecting AI to email, the CRM or the bank account with the same access the owner has is the fastest way for a small mistake to become expensive. Reading, proposing and executing are not the same permission.
Who it is for
Owners and technical leads of small businesses about to connect an assistant, an AI automation or an agent to real business tools.
Fill in the checklist before granting the first access, not after. It takes 10 minutes per tool and forces you to answer the question almost nobody asks: if this goes wrong, can it be undone?
The protocol, step by step
-
Inventory the connections
List every tool the AI will touch and what you want it to do in each.
Copy and pasteTool · what it needs it for · data it will see · actions it will take
-
Separate read, propose and execute
For each action, mark the level. Read: only looks things up. Propose: leaves a draft a person approves. Execute: acts on its own. Start everything at read or propose.
-
Grant minimum access and only essential data
Create a dedicated user or access key for the AI; never use the owner's account. Limit it to the folders, labels or tables it needs. If the tool allows read-only permissions, use them.
-
Classify each action: reversible or not
Actions that move money, change prices, delete data, publish on behalf of the brand or write to important customers are never executed without human approval. Reversible ones (create a draft, tag, create a task) can run on their own once you have evidence.
-
Log everything
Every action must leave a record you can read without being technical.
Copy and pasteDate and time · tool · what the AI decided and why · user or customer affected · result · who approved (if applicable)
-
Set limits, alerts and a stop button
Define a daily cap (messages sent, records changed, spend), an alert when it gets close and a way to shut everything off in one minute: disable the flow or revoke the access key. Write down who can press it.
-
Review the checklist with AI before connecting
Paste your inventory with this prompt to find gaps.
Copy and pasteI am going to connect an AI to these tools: [PASTE INVENTORY WITH READ/PROPOSE/EXECUTE LEVEL]. Point out: actions that should move down a level, irreversible actions without human approval, data that does not need to be shared, and what is missing in logging, limits and the stop button.
Common mistakes
- Connecting AI with the owner's account or an admin key.
- Granting execute from day one "to test it". Test in propose.
- Having no quick way to turn it off. If you do not know how to stop it in a minute, it is not ready.
- Sharing full customer databases when the task only needs name and order status.
Who this is NOT for
It does not replace a security audit or compliance with your country's data protection law. It is the minimum checklist an owner can review without being technical.
Want it applied to your business?
If you would rather not build it alone, book 30 minutes with me and we will review it with your real case. If you still do not know where to start, the map tells you what to automate first in 5 questions.