AI Impact HubConnectors
AI that can see your work is a different tool entirely.
For the person who spends half of every AI session copy-pasting context in.
Try it right here ↓Free, like everything in the Hub. No signup to read it.
Out of the box, AI knows exactly what you paste into it. Connectors change the deal: link it to Drive or Microsoft 365, your email, your calendar, your CRM — hundreds of platforms now — and it stops asking you to copy things in and starts working with where your work already lives. Kyle teaches them in the same breath as the second brain: point, don't duplicate.
A connector is permission with a pipe attached. Instead of you fetching documents for the AI, the AI fetches them itself — your policies from Drive, this morning's emails, next week's calendar — always the current version, never the copy you pasted in March. In Kyle's phrase, the chat becomes more of a hub connecting you to your tools.
His cleanest frame for the whole space: taking the AI to Gmail versus putting AI in Gmail. Copilot and Gemini put AI inside the tools you already work in; connectors bring those tools to your AI. Plenty of organisations sensibly run both — one for working inside a document, one for working across everything.
The permissions are the real teaching. Every connection exposes its abilities verb by verb — read, draft, create, delete — and each one can be allowed, need approval, or be blocked. Some are governed for you: Gmail can draft, and cannot send. Others are blunter than you expect — Drive access is all files or none, with no way to scope it to a folder, which is exactly why the honest setting for reading is needs approval.
This is where AI stops being a private experiment and starts touching organisational data — which is why Kyle's cohorts get it as literal homework: leaders, make sure your AI policy covers connectors; everyone else, read what your policy says before you plug anything in.
Once you give it access to your Google Drive, it can potentially read any file in your Google Drive. If you've got an AI policy that says some data should not be presented to AI, this is where you really want to be cautious — change this to needs approval. The AI will ask before it reads: am I allowed to look into this file? And you can say yes or no.Kyle, inside the permissions screen during a live webinar, June 2026.
- Check the policy firstThe AI policy template in the library has a connector clause for exactly this moment. If your policy predates connectors, it does not cover them.
- Browse, connect, authenticateConnectors live behind the plus button. Pick the platform, sign in on its own site, and it joins your connections list. The connecting is the easy part.
- Set the permissions, verb by verbAllowed, needs approval, blocked — for each ability, deliberately. If any data in Drive is off-limits to AI, reading needs approval. Drafting can be allowed while deleting stays blocked.
- Tell it which connector to useFrom Kyle's own demo, where the AI coded a graphic instead of opening Canva: sometimes it won't use your connectors unless you actually tell it to. Name the tool in the prompt.
- Point, don't duplicateThe second brain rule: if it already lives in Drive or SharePoint, connect to it there. Copies go stale; sources don't. This is also what makes agents and scheduled tasks possible — they need to reach the real systems.
Four statements before you plug anything in. Score honestly — this is the pre-connection check Kyle's homework implies.
Our AI policy explicitly covers connectors and integrations.
Not AI in general — connectors specifically: which systems may be linked to AI tools, and who approves it.
We know where our sensitive data actually lives.
Client records, HR, finance — named systems and folders, not “somewhere in Drive”.
Access inside those systems is already scoped.
People see what their role needs. Nothing important is on an everyone-can-view link from 2021.
We could name every connection we've enabled, and switch one off today.
Somebody owns the list. Unplugging is a decision, not an archaeology project.
Nothing scored yet — start at the top.
Next: Skills.
Do the work first. Then turn it into a skill.
Read Skills →