Fetching live does not mean zero retention
Results can still be included in chats, logs, or other retained records. Check the policies of each service in the path.
APP PERMISSIONS & AI CONNECTORS
See what you’re letting in.
Understand what an app or AI assistant can access before you click Allow.
01
Explore a connection
Connecting ChatGPT, Claude, or another AI assistant gives it a path into your apps.
Explore the settingsIllustrative example
Match these to the request you see. Availability varies by connector and account.
No accounts connected. No data scanned.
YOUR APPS → YOUR AI ASSISTANT
One connection. More to consider.
“Summarize my client meetings this week.”
DataResults
Actions pause for your approval
01
Shared information can be included too.
This example allows broad access within the grant and source permissions. Existing messages, attachments, or shared documents can be in reach. Your current chat does not define the whole permission boundary.
Example content: Client emails, attachments, meeting notes.Connecting and acting are separate
Granting account access and approving a specific action are different steps. Review the tool and what it will send or change.
ONE AI-SPECIFIC RISK
An instruction hidden in the content
An email, document, or tool result can contain text that tries to redirect the assistant. This is called prompt injection.
Project notes.txt Fictional example
The project review is scheduled for Monday.
BEFORE YOU CONNECT
0 / 5 reviewedFive checks to take with you
Mark an item only after reviewing it. Changing the settings resets this checklist.
Provider guidance & how to use these examples
These scenarios illustrate capabilities, not the default permissions of a named product. No connector is inspected or verified. Check the actual request, account plan, administrator policy, and available tools. Sources reviewed September 6, 2026.
Microsoft distinguishes connectors that index data from those that retrieve it live. OpenAI and Anthropic document tool permissions, approvals, and prompt injection risks. Exact behavior varies by product.
OpenAI: MCP access, approvals & prompt injection OpenAI: plugin permissions & data handling Claude: custom connectors, permissions & removal Microsoft Copilot: synced & federated connectors01
Check the permissions
Use the permission text or a screenshot from a Microsoft or Google access request.
English permission wording or scope names
OR EXPLORE AN EXAMPLE
YOUR ACCESS MAP
Follow the permissions.
Email assistantFICTIONAL EXAMPLE
Access requested Not found Select an area
4 permission types recognized Based only on the supplied request
YOUR EMAIL
email access: read & send.
Select an action to see what the requested permission could allow.
SEE IT IN PRACTICEFictional data
Inbox
From Jordan Lee <[email protected]>
Subject Project notes for Monday
The draft proposal and client meeting notes are attached.
The app can read this message and its attachment.
Before you allow it, ask
- Does the app need your whole inbox, or only messages you choose?
- Do you approve each message before it is sent?
This explains requested access. It does not verify the app or prove what it actually does. An app may retain information it has already copied.
Sources and recognized permissions (4)
The English wording and scope names are matched against a curated reference. Unrecognized text is kept for your review. Reference reviewed September 6, 2026.
https://www.googleapis.com/auth/gmail.readonlyView your email messages and settingshttps://www.googleapis.com/auth/gmail.sendSend email on your behalfhttps://www.googleapis.com/auth/drive.readonlySee and download all your Google Drive fileshttps://www.googleapis.com/auth/userinfo.emailSee your primary Google Account email address