Access, Ownership, and Handoff
Make sure your partner owns the accounts, controls access, and can run the automation without you.
Objective
By the end of this lesson, you can set up an automation so your partner owns it, access is limited, and a handoff document explains how it works.
Your partner owns it, not you
A common mistake: a builder makes the automation in their own personal account. Then the builder moves on, and the business loses control of its own system.
The rule: build in an account the organization owns. Use an organization email to sign up for the tool. Add yourself as a helper if needed, then remove yourself at the end.
Least access
Least access means each person and each tool gets only the access it needs, and nothing more.
- If the automation only needs to add rows, do not give it access to the whole Google Drive if the tool lets you choose.
- If a volunteer only needs to see the schedule, share a view-only tab, not the full sheet.
- Never paste a password into a sheet, a chat, or a prompt. Use the tool's built-in connection screen.
When you connect an app, the tool asks for permissions. Read the list. If a permission looks bigger than the job, ask why.
A note on AI agents and data connections
Newer tools let AI assistants read data directly from business apps. One standard for this is called MCP, the Model Context Protocol. It is a shared way for AI tools to connect to apps like spreadsheets, payment systems, or analytics, with access rules managed in one place.
The idea is good: one hub with clear permissions, instead of passwords scattered everywhere. The same judgment applies. Give the AI read-only access when it only needs to read. Keep a log of what it touched. Do not connect it to sensitive or youth data.
Go deeper: MCP Dashboards vs. The Old Way by Dom Davis, Temerarii Media.
The handoff document
Your handoff document is a one- or two-page guide your partner keeps. It should answer:
| Section | Answers |
|---|---|
| What it does | One plain paragraph and the workflow map |
| Accounts | Which tool, which account owns it, who can log in |
| Data | What data flows where, and what never goes into AI |
| Human steps | What a person must still check or approve |
| When it breaks | Who gets alerts, the manual backup, who to call |
| How to turn it off | The exact steps to pause it |
That last row matters most. Your partner must always be able to turn it off.