The AI Marketing Permissions Map

01 The three checks the dashboard did

Marketing tools are going headless: you stop opening the tool and ask your AI assistant to work it for you. The plug that makes this possible is called an MCP server, or a connector in Claude and ChatGPT. Movable Ink, CreatorIQ, Hightouch, Klaviyo, HubSpot and Customer.io all have one, live or on the way.

The dashboard you're about to stop opening was doing three jobs, and nobody wrote them down:

Who. The audience count, right before you sent. Eighty thousand people, when you expected eight. What. The preview, where you catch the wrong price or the typo in the subject line. When. The send button. The last moment where a person decides.

The brakes exist in these tools. They're just not always on. This map is where you write down, tool by tool, which ones are.

02 The map, one row per tool

In Claude, each connector's tools can be set to Always allow, Needs approval (it shows you the action and waits for your yes) or Blocked. The rule from the film: let it read freely, put anything that writes on Needs approval, and block the send and the spend.

Tool What its own docs say

Klaviyo Creates campaigns as drafts a human checks. Scheduling and sending from the chat was "expected" in Q3 2026 in its agency guide; check what yours can do now. You can leave out the tools that read user-generated content.

HubSpot (ChatGPT) Can create and update CRM records. Recommends setting write tools to "Needs Approval." Changes are logged in the audit log under your name and the connector's.

Customer.io Starts read-only. Writing is something you choose to turn on.

Hightouch Chains tools: a report sent to Slack, an audience synced to Braze. Every hop is a place a screen used to be.

Movable Ink More than 50 APIs open to Claude, ChatGPT, Gemini and Cursor. Early access.

CreatorIQ Q Only the analytics agent is live; the full version is due early 2027. Actions stay inside the approval thresholds a brand sets.

Permissions map row (one per tool)

Tool: [TOOL]
Connected to: [Claude / ChatGPT]
Connected with whose login: [NAME, ROLE: admin or not?]
Read (Always allow): [e.g. reports, audiences, past campaigns]
Needs approval: [every tool that creates, updates or drafts]
Blocked: [send, schedule, spend]
Tools that read strangers' content: [list] Switched off? [yes / no]
Checked on: [DATE] by [NAME]

Whose login is it? A connector reaches whatever the account behind it can reach. Connect with an admin login and your assistant has an admin's reach. In HubSpot, an agency or consultant with super admin rights can connect it themselves.

03 An owner for who, what and when

Each check needs a new home: a setting, or a person.

Who: name the person who decides the audience. Who counts as active, who gets suppressed, who never gets the email. If you manage several accounts, Klaviyo recommends one Claude project per account with a standing line naming the right account.

What: set every writing tool to Needs approval. Check what yours says today instead of assuming.

What: switch off tools that read strangers' content, where you can. A support ticket or form can carry instructions a poorly guarded agent might follow.

When: block the send and the spend. Keep them blocked until you've watched everything else work for a while. On Claude's Team and Enterprise plans, an owner can set these limits for the whole company.

04 The two-week rollout

Week one: read-only, audits only

Customer.io suggests keeping writing off for the first week. Use it to ask questions and run audits. The best first job is finding what's broken before it ships. When the agency Sticky Digital asked Klaviyo's agent to audit a client's welcome emails, it flagged 17 issues, ranked, including a typo on three messages. Every account still gets two checks: one from the agent, one from a person.

Week two: drafts, with your approval on every write

Let it draft. Approve each write before it happens. The send and the spend stay blocked.

Every week after: read the log

Weekly log check

Week of: [DATE]
Who connected what this week: [NAME] connected [TOOL] to [ASSISTANT]
What it changed: [RECORDS / DRAFTS / AUDIENCES]
Anything it changed without an approval? [yes / no: which]
Any setting that moved off Needs approval? [yes / no]
One fix for next week: [ACTION]

You're not logging in less. You're approving more.

Sources

Klaviyo: MCP Server Guide For Agencies Klaviyo: MCP Server Klaviyo blog: How to Train Your AI Marketing Agent (Sticky Digital) HubSpot: Set up and use the HubSpot connector for ChatGPT Customer.io: Marketing MCP servers Claude Help Center: Use connectors to extend Claude's capabilities Hightouch Docs: Hightouch MCP Movable Ink: Introduces Headless Marketing Capabilities Movable Ink blog: Introducing AI Assistants and MCP CreatorIQ: Unveils Q

Mathew's LibraryLibrary card

Free access

Keep reading free with your library card

One email opens this template and all 86 resources in Mathew's library. No account, no password.