AI Connection RegisterTemplateTemplate

Template for recording every AI connection: which account, which tool, read or write, where the keys live and when to review it.

What you get (+1 bonus)

One row per connection.
One source account connected to one AI tool or vendor is one row. Three illustrative rows, for Meta, GA4 and Shopify, show how a filled-in register reads.
Fourteen columns, with examples.
From the account and the AI tool to the role it signs in with, read or write, personal data, where keys are stored and how to revoke it at both ends.
A 10-minute quarterly review.
Six checks for every row once a quarter, from whether each connection still has an owner who works for you to anything connected that isn't in the register.
When someone leaves.
Five steps that remove a leaver's users, disconnect their rows at both ends, replace the keys they could reach and check their last two weeks of changes.
+1 bonus
An AI skill for Claude, ChatGPT, Gemini or Copilot
that builds the register with you from what you tell it or a list your team put together, then scores each row on the 15 checks.

Free · about 15 seconds

Who it's for, and who it's not for

A marketer at a desk is about to click an approval button on a laptop sign-in screen.

Who it's for

Shops and lead-gen businesses with more than one AI connection to their ad accounts, analytics or store, who want one place that says who connected what.
Owners and team leads who need to cut off a leaver's AI access quickly, including connections made through a shared user or a vendor account.
Agencies and freelancers keeping track of client accounts connected to AI tools, with an owner and a review date for each one.

Who it's not for

Anyone with no AI connections yet. Start with the checklist and the five-minute routine, then add the first row on the day you connect.
Teams that already log every integration in a formal access-management system - add the AI-specific columns there instead of keeping a second list.

What's inside

PDF · 1 table

Honest note

The register only knows what someone writes in it, so add a row on the day a connection is made and review every row once a quarter. Removing a person's platform access doesn't cut off connections made through a shared user or a vendor account. Revoking still happens at both ends, in the platform and in the AI tool. This is practical guidance, not legal advice.

Free · about 15 seconds