Home › Claude Security & Privacy Center for Business Owners › Security questions › We want people to upload files to Claude by hand, never let Claude reach into our shared drives, and restrict some files. Can Claude Team do that?

Admin controls

We want people to upload files to Claude by hand, never let Claude reach into our shared drives, and restrict some files. Can Claude Team do that?

Short answer

Mostly yes: Claude Team can run upload-only with no shared drive access. On Claude Team the owner decides whether the Google Workspace and Microsoft 365 connectors exist at all, only owners can add custom connectors, and the desktop file-access feature (Cowork) can be switched off for the whole organization. With managed devices you can also limit which folders the desktop app may open. What Team does not do is inspect a file and block it by content. Restricting specific files is a job for your file permissions and your written rules. The settings are walked through in the admin controls that keep Claude Team secure.

We want people to upload files to Claude by hand, never let Claude reach into our shared drives, and restrict some files. Can Claude Team do that?

What the rules and Anthropic actually publish

Anthropic’s Google Workspace connector article: on Team and Enterprise, an Owner or Primary Owner must enable the connectors at the organization level, and owners can turn them off in Organization settings > Connectors. Anthropic’s Microsoft 365 connector security guide describes the same owner step, plus consent from a Microsoft Entra Global Administrator.
Anthropic’s remote MCP article: custom connectors “only Owners and Primary Owners can add them to Team plans.” Members cannot wire Claude to a new system on their own.
Anthropic’s Cowork on Team and Enterprise article: an Owner or Primary Owner can “toggle off to disable Cowork for all users in your organization.” Turning Cowork on for specific groups is described for Enterprise, not Team.
Anthropic’s desktop configuration article: Team and Enterprise admins can control the desktop app through system policies, including allowedWorkspaceFolders (“Filepath or filepaths the user can mount to Cowork”), a switch for local MCP servers, and a switch for desktop extensions. These are pushed through Group Policy or Intune on Windows, or a configuration profile on Mac.
The same security guide: where the connector is on, access is delegated, so users only reach files they already have permission for and “cannot bypass SharePoint sharing settings or folder permissions.”
Anthropic’s audit log article: “Audit logs are available for Enterprise organizations only.” The pricing page lists role-based access, network-level access control and IP allowlisting as Enterprise additions.

The follow-up questions owners ask

Is uploading files to Claude by hand safer than a Google Drive or SharePoint connector?

The data terms are the same: an uploaded file and a connector read are both covered by Anthropic’s commercial terms and are not used for training by default. The difference is control. With uploads, a person picks every file, and nothing outside that choice is in reach. The uploaded file lives in that chat until the chat is deleted, so your deletion routine still matters.

How do I keep specific files out of a Claude Team upload-only setup?

Claude has no way to know a file is “restricted” unless someone tells it. Keep those files where Claude has no route: not in any folder the desktop app can open, and not in a drive a connector can see. Then write the rule into your usage policy and the organization instructions, for example “never upload anything from the HR or Payroll folders.”

In a Claude Team upload-only setup, can I limit desktop folder access without Intune or device management?

Not with the folder policy, because it has to be pushed to each computer by device management. Without it, the dependable choice is to turn Cowork off in Organization settings until you need it. If you do turn it on, train each person to attach one working folder only.

Will a Claude Team owner know if staff break the upload-only rule?

Not from Claude on Team, because there is no audit log. The Primary Owner can export the organization’s data after the fact, and your file systems keep their own access history. If a client contract requires a reviewable log of AI activity, that points to Enterprise.

What this means for your rollout

In Organization settings > Connectors, turn off Google Workspace, Microsoft 365 and any connector you are not using before the first seat is assigned.
Keep the Owner and Admin roles to one or two people so nobody else can add a connector.
Turn Cowork off at the start. Turn it on later with allowedWorkspaceFolders if you have device management.
Move restricted files into folders that are never attached or connected, and list those folders by name in the usage policy.
Train staff on one rule: upload only what the task needs, from the approved locations.
Michael’s two cents

A consulting-firm owner asked me this nearly word for word, and it is a sensible way to start. Upload-only gives up some convenience, but the owner can explain the whole setup to a client in two sentences. I usually run this pattern for the first few months, then open one connector to one folder once the team has proven the habits.

Related services and tools

Admin controlsthe ten Team settings and the order to set them.
Secure Claude implementationsettings, desktop installs and staff training as one project.
Claude security for consulting firmsclient NDAs, matter walls and what to tell procurement.
Team vs Enterprisewhen audit logs and group controls justify the upgrade.

Get the plan before you buy the seats

The plan choice is the easy part. Configuration, governance and training are where firms get it wrong. The Claude Build Plan is two working sessions with Michael Robichaud, then a written plan: architecture, plan choice with the reasons, your firm’s custom Claude plugin scoped, rollout timeline and cost. A fixed , and the plan is yours to keep.

Get the Claude Build Plan or book a 20-minute intro call.

Related questions

Sources

Michael Robichaud

About the author

Michael Robichaud, Founder of Strategized.ai, sets up Claude for small firms that handle client data: CPA and tax firms, law firms, RIAs, insurance agencies and medical practices. Nearly 30 years in enterprise software sales (RSA Security), digital marketing and technical SEO, and two companies built and sold. Every source on this page was checked against Anthropic’s published documentation and the regulator’s own text.

Book a short call about your firm How a secure setup works

Not legal advice. Confirm regulatory items with your counsel. Anthropic pages change; every source above shows the date we checked it.
Strategized.ai is independent and not affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.