Troubleshooting
Permission Denied: Why Cowork Can't Access Your Files (and How to Fix It)
Claude Cowork says it can't read or write your folder? Here's why macOS and Windows block it, and the exact steps to fix each cause.
Quickest fix: On macOS, go to System Settings > Privacy & Security > Files and Folders, find Claude, and enable access to the folder type you're working in.
You pointed Cowork at a folder and it came back with a permission error. The folder is right there, you can see it in Finder or Explorer, and yet Claude is acting like it doesn’t exist. This is not a bug in Cowork so much as a modern OS doing exactly what it was designed to do: keeping software out of your files until you say otherwise. The good news is that the fixes are mostly a few clicks, once you know which door to unlock.
Quickest fix (macOS): Open System Settings, go to Privacy & Security, scroll to Files and Folders, find Claude in the list, and check the box next to whichever location you're trying to use (Desktop, Documents, Downloads, or a specific folder). Restart Claude after saving.
Why This Happens
Modern operating systems treat file access as a privilege that apps have to request and that users have to approve. On macOS, this system is called the Privacy & Security framework. On Windows, the relevant feature is called Controlled Folder Access (part of Windows Security). Both are designed to stop malicious software from silently reading or changing your files. They work, and they work indiscriminately, which means a perfectly trustworthy tool like Cowork gets blocked the same way a piece of malware would until you approve it.
There are a few distinct causes, and each one has a different fix.
macOS: Files and Folders Permission
This is the most common cause on Mac. Apple requires apps to request permission before touching certain standard locations: Desktop, Documents, Downloads, and a few others. If you launched Cowork and immediately pointed it at your Documents folder without approving the permission prompt (or if you clicked “Don’t Allow” by accident), it simply cannot see those files.
How to fix it:
- Open System Settings (the gear icon, not System Preferences, that’s the old one).
- Click Privacy & Security in the left sidebar.
- Scroll down to Files and Folders.
- Find Claude in the list. If it’s not there, Cowork hasn’t tried to request access yet, try the next section.
- Enable the toggle for whichever location you need: Desktop Folder, Documents Folder, Downloads Folder, or Removable Volumes.
- Quit Claude fully (right-click the Dock icon, choose Quit, not just close the window).
- Reopen Claude and try the task again.
If Claude doesn’t appear in the Files and Folders list at all, the permission prompt may have been dismissed before it could be recorded. Try this: in the Cowork session, ask it to read a specific file in the blocked folder. macOS will prompt again. Approve it, then restart Claude.
macOS: Full Disk Access (for Protected Locations)
A few locations on macOS are protected beyond the standard Files and Folders permission. These include your Mail data, Time Machine backups, and some system directories. If Cowork needs to work in one of those areas, it needs Full Disk Access.
How to fix it:
- Open System Settings > Privacy & Security > Full Disk Access.
- Click the plus button and navigate to Claude in your Applications folder.
- Add it to the list and make sure the toggle is on.
- Restart Claude.
A word of honest caution: Full Disk Access is a broad grant. You’re telling macOS that Claude can read from almost anywhere. Cowork’s own folder-scoping still applies (it only works inside what you’ve shared in the session), but you should understand what you’re granting at the OS level. See Anthropic’s privacy documentation for how data is handled.
macOS: iCloud and Cloud-Only Files
If your files are stored in iCloud Drive and you have “Optimize Mac Storage” turned on, macOS may have offloaded some files to the cloud to save local disk space. The file appears in Finder with a little cloud icon, but the actual bytes are not on your machine. Cowork cannot read a file that isn’t there.
How to fix it:
- Open Finder and navigate to the file or folder.
- Right-click and choose “Download Now” (or click the cloud icon next to the file).
- Wait for the download to complete. The icon will change from a cloud to a normal document.
- Try the Cowork task again.
If you work with iCloud-stored files regularly, consider turning off “Optimize Mac Storage” for the folders you use with Cowork: System Settings > Apple ID > iCloud > iCloud Drive > Options.
macOS: OneDrive and Other Sync Services
OneDrive has its own version of the same problem. Files-on-demand means files that aren’t actively synced appear as placeholders. The fix is the same: open the file in its native app or right-click in Explorer and choose “Always keep on this device” for the relevant folder, then retry.
Dropbox and Google Drive can also cause this if you’re using their selective sync features. Check the sync app’s status indicator in the menu bar before assuming it’s a Cowork problem.
macOS: Folder Permission Bits
Less common but worth checking: the folder itself might have restrictive Unix permissions. This usually happens with folders created by another user account or copied from a server.
How to check and fix it:
- In Finder, right-click the folder and choose Get Info.
- Scroll to the Sharing & Permissions section at the bottom.
- Check that your user account has Read & Write permission.
- If not, click the lock icon, authenticate, and change the permission for your account.
Alternatively, in Terminal: ls -la /path/to/folder will show you the permission bits. chmod 755 /path/to/folder is a reasonable starting point for a folder you own.
Windows: Controlled Folder Access
Windows Defender’s Controlled Folder Access blocks unauthorized apps from writing to protected folders like Documents, Pictures, and Videos. If Cowork tries to write a file to a protected location, it will be blocked silently or with a generic access denied error.
How to fix it:
- Open Windows Security (search for it in Start).
- Click Virus & Threat Protection.
- Click Manage Ransomware Protection.
- Under Controlled Folder Access, click “Allow an app through Controlled Folder Access.”
- Click “Add an allowed app” and browse to the Claude executable. It’s typically in
C:\Users\<YourName>\AppData\Local\AnthropicClaude\. - Save and retry the task in Cowork.
Note that Claude updates can change the executable path. If Cowork starts getting blocked again after an update, re-check this setting and re-add the new path.
Windows: Folder Permissions on NTFS
If you’re working with a folder that was created by an admin account, a company policy, or copied from another machine, your user account might not have write permission on it.
How to fix it:
- Right-click the folder in Explorer and choose Properties.
- Click the Security tab.
- Check if your user account (or the Users group) has Read and Write permissions.
- If not, click Edit, add your account, and grant the needed permissions.
- Click Apply and OK.
If your machine is managed by an IT department, they may have locked certain folders intentionally. In that case, the fix is a conversation with IT, not a settings change on your end.
Still Stuck?
If none of the above resolves it, check the Claude Help Center for platform-specific updates. Permission behavior can change with OS updates, and Anthropic publishes notes when a workaround is needed. You can also check Anthropic’s GitHub for open issues related to file access on your platform.
One last thing worth saying plainly: if a fix requires granting broader OS permissions than you’re comfortable with, it’s reasonable to not grant them. Cowork is designed to work within whatever scope you allow. The session-level folder sharing is a second layer of control on top of the OS permissions, so you have more than one place to set limits.
Frequently asked questions
Does giving Claude full disk access mean it can read everything on my Mac?
Full Disk Access lets Claude read protected locations like Mail and Time Machine backups, but Cowork still only works inside the folders you have explicitly shared with it in the session. The OS permission and the Cowork folder scope are two separate gates.
My file is in iCloud Drive and Cowork says it can't read it. What's happening?
iCloud Drive uses on-demand downloading, so files that haven't been opened recently exist only as placeholders on disk. Cowork can see the placeholder but not the contents. Open the file in Finder first so macOS downloads it, then try again.
I fixed the macOS privacy setting but Cowork still gets the error. Why?
Privacy permission changes often don't take effect until the app is fully restarted. Quit Claude from the menu bar, wait a few seconds, and reopen it.
Windows Controlled Folder Access keeps blocking Cowork even after I added it as an allowed app. What now?
The Windows Security app sometimes requires you to remove the entry and re-add it after a Claude update, because the executable path can change with new versions. Re-add Claude's current executable path in the Controlled Folder Access settings.
Can Cowork access network drives or external hard drives?
Yes, with caveats. On macOS, network volumes and external drives may need separate Files and Folders permission grants. On Windows, mapped network drives work if the drive letter is accessible to the account running Claude. Slow or intermittent network connections can also produce permission-style errors that are actually timeouts.