What this tutorial solves
Connectors look like “more is better” but every connector you enable expands what Claude can see, indexes, and accidentally summarize back at you. The right setup is minimum scope plus a clear use-case per connector. This guide walks through what to enable, how narrow to scope, how to test for permission leaks, and how to revoke before they bite. Audience: Claude Pro / Team users who connected Drive once, saw it work, and now have eight connectors they cannot remember authorizing.
Who this is for
Claude Pro / Team users with Gmail, Google Drive, GitHub, Slack, Notion, Jira, or similar work tools that have Claude connectors available. Especially valuable if you share an account with family, or if your work email has personal content.
When to reach for it
A recurring task involves the same external tool (drafting based on email, searching docs in Drive, checking GitHub issues, summarizing Notion pages). For one-off tasks, uploading the file directly is faster and lower-risk than authorizing a full connector.
When this is NOT the right tool
Personal accounts with sensitive data unrelated to work; shared / family accounts (your spouse’s calendar should not be in Claude’s context); one-off tasks where uploading the relevant file is faster than connecting; any tool with PII or financial records you don’t want sent to Anthropic.
Before you start
- Read the data-handling section of your Claude plan. Free / Pro / Team / Enterprise differ on training, retention, and audit. Decide what you are willing to send.
- List the external tools you use weekly. Mark which ones contain mostly work content and which mix work + personal.
- Pick a single connector and a single use-case for your first install. Resist the urge to add three at once.
- Have a teammate or alt account available for the permission-leak test in step 6.
Step by step
- Start with ONE connector and one use-case. Add more only when the first proves useful. Most people end up using 2-3 connectors heavily and ignoring the rest.
- In the connector permissions screen, choose the narrowest scope offered (specific folders, specific labels, read-only when possible). If the only option is “all”, treat it like a screen share — limited sessions, not always-on.
- Test the connector with a benign query first:
List the last 5 emails from a specific coworker. Verify it returns what you expect. If results look like more than you authorized, revoke and re-scope. - Build a default prompt template that uses the connector explicitly:
Search Drive for a named topic and summarize the 3 most recent files.Save these in a notes app. - Audit connector access monthly. Open Claude’s connector settings, revoke anything you haven’t used in 30 days. Connectors decay in value but not in permission scope.
- For shared workspaces, get a teammate to test from their account — permissions can leak in subtle ways. If they can see your private files via Claude, the connector scope is wrong.
First-run exercise
- Connect Google Drive scoped to a single folder named “AI experiments”. Add 3 sample files there.
- Ask Claude:
List the files in my AI experiments folder and summarize the most recent one in 5 bullets. - Verify only those 3 files appear. If Claude can see anything outside that folder, re-do the OAuth scope.
- Try a second prompt that references the folder by name. Confirm responses stay grounded in those files, not invented summaries.
Quality check
- Does the connector return only the files / messages you authorized? Anything broader means the OAuth scope is wider than you thought.
- Are responses grounded in the source — quoting, citing, naming files — or paraphrased generically? Generic answers indicate the connector didn’t return useful results.
- Watch latency. Connectors that take 10+ seconds per query are usually too broad; narrow scope.
- Periodically test from a private window or alt account to confirm permissions did not silently expand after an update.
How to reuse this workflow
- For each connector, save its use-case, scope, and template prompt in a notes file. When you re-evaluate next quarter you will remember why you set it up.
- Build a 5-minute monthly audit ritual: open connector settings, count, revoke any not in use, re-test the rest with a benign prompt.
- For competitor / research connectors, run the same prompt weekly — the prompt becomes a heartbeat that tells you the connector is still working.
- Maintain a “deny list” of tools you decided not to connect, with the reason. Stops you from re-evaluating the same decision every six months.
Recommended workflow
Weekly competitor research: Drive connector indexes a “competitors” folder. Each Monday, prompt: Find new files added in the last week, summarize key claims, flag anything contradicting our positioning. Save the summary to Notion. Disconnect when you go on extended leave.
FAQ
- Are connectors safe?: Functionally yes, but trust is a sliding scale. Read the data-handling section of your Claude plan before connecting anything sensitive.
- Why is my connector slow?: Each query hits the external API. Large folders or noisy email accounts compound latency. Narrow the scope.
- My connector worked yesterday and now Claude says it does not have access.: A connector that silently dropped its OAuth grant or a tool that was disabled for your plan can both surface as “I don’t have that tool” — see Claude tool unavailable.
- Can connectors write back to my tools?: Some can (create Notion pages, post to Slack); read carefully which permissions are read-only vs read-write before authorizing.
- What happens if I switch plans?: Connector availability changes between Pro / Team / Enterprise. Your authorizations persist but specific tools may disable.
- How do I fully revoke a connector?: Revoke in Claude AND in the source tool’s OAuth-apps page. One without the other leaves grants lingering.
Common mistakes
- Authorizing “full Drive access” when you only need one folder.
- Forgetting that connector-fetched content goes through Claude — sensitive emails should not flow through if your plan does not promise no-training.
- Connecting and then never building a workflow around it. The connector adds latency to every chat for no benefit.
- Letting connector results bypass review. Always sanity-check before acting on summaries.
- Mixing personal and work data in the connected account — Claude does not distinguish.
- Authorizing during a busy moment and never re-checking scope. Initial OAuth screens are designed for “approve and move on”.
Advanced tips
- Name your connector use-cases (“Drive: competitor research”, “GitHub: weekly PR review”). Helps future-you remember why you connected.
- For email-based connectors, restrict to a specific label or sender to keep noise out.
- Disconnect before going on vacation if you do not want Claude pulling current data while you are away.
- Use a dedicated “AI-shared” folder in Drive / Notion as the connector surface. Move things in deliberately; nothing leaks by accident.