APP PERMISSIONS & AI CONNECTORS

See what you’re letting in.

Understand what an app or AI assistant can access before you click Allow.

Free to use. No account needed.

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.

What can it do?

How much can it reach?

How does it get the data?

Before taking an action

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

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.

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.

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

Five checks to take with you

0 / 5 reviewed

Confirm who operates the connectorCheck the publisher and server address. A familiar service name does not identify who runs the connection.Reduce the reachable dataCheck the consent screen and source permissions. Include existing shared content, not just files or messages you create next.Check what is retained after retrievalReview retention, training use, and deletion terms for your exact AI plan and the connector operator. Disconnecting is not a promise to erase earlier copies.Review each action before approvingCheck the exact tool, recipient, destination, and content. Account consent and approval of an individual action are separate controls.Know how to stop accessFind the disconnect control in the assistant and the account grant in the source service. For work data, confirm your organization permits this connection.

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 connectors

Check the permissions

Use the permission text or a screenshot from a Microsoft or Google access request.

Provider

English permission wording or scope names

OR EXPLORE AN EXAMPLE

YOUR ACCESS MAP

Follow the permissions.

Example

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 <jordan@example.com>

Subject Project notes for Monday

The draft proposal and client meeting notes are attached.

The app can read this message and its attachment.

Read your email

Read email content and attachments, including messages that contain personal or client information. This permission does not grant sending or deleting email.

Permission reference

Send email as you

Send messages from your Gmail account. This permission alone does not let the app read your inbox.

Permission reference

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 settings

https://www.googleapis.com/auth/gmail.sendSend email on your behalf

https://www.googleapis.com/auth/drive.readonlySee and download all your Google Drive files

https://www.googleapis.com/auth/userinfo.emailSee your primary Google Account email address

Microsoft Graph reference ↗
Google permission scopes ↗