Manatee

"The file couldn't be opened because you don't have permission to view it"

· 7 min read

“The file couldn’t be opened because you don’t have permission to view it” means macOS stopped an app from reading the file. The file itself is almost never damaged. Two different gatekeepers produce the same words: the file’s own permissions, which say which user accounts may read it, and the privacy settings that decide which apps may reach folders such as Desktop, Documents and Downloads. A quick test tells you which one you are dealing with.

Two kinds of permission behind one message

File permissions belong to the file. Every file and folder records an owner, a group and everyone else, each with a privilege: Read & Write, Read only or No Access. If your account is not allowed to read the file, no app you run can open it. This is the usual story for files copied from another user account, brought over from an older Mac or restored from a backup.

App permissions belong to the app. macOS asks before an app first reaches into Desktop, Documents, Downloads, a removable drive or a network volume. Click Don’t Allow once and that app is refused from then on, with this same message, even though the file’s own permissions are fine.

Find out which one it is

Select the file in Finder and press the Space bar for Quick Look, or open it in a different app.

  • It opens elsewhere. The file’s permissions are fine and the first app is being blocked. Go to the section on the app’s access.
  • Nothing can show it. The file’s permissions are the problem.

For detail, select the file, choose File, Get Info, and open Sharing & Permissions. The list shows each name with its privilege, and the line above the list states what your own account can do. Terminal shows the same thing on one line. Type ls -le and a space, drag the file in, and press Return:

ls -le ~/Documents/report.pdf
-rw-------  1 olduser  staff  48213 Mar  3 10:12 report.pdf

The name in the third column is the owner. The letters at the start are the rights: the first rw- belongs to the owner, the next three characters to the group, and the last three to everyone else. In this example only the owner can read the file. If that owner is not the name that whoami prints, you have found the cause. A number in place of a name means the owner was an account on another Mac.

Fix the file’s permissions

In Finder. You need an administrator’s name and password.

  1. Select the file and choose File, Get Info.
  2. Open Sharing & Permissions and click the lock at the bottom of the window to unlock it.
  3. If your name is in the list, set its Privilege to Read & Write. If it is not, click the plus button, choose your account, click Select, then set Read & Write.
  4. For a folder, open the action menu (the circle with three dots) and choose Apply to enclosed items, so the change reaches everything inside.

In Terminal. For a single file:

sudo chown "$(whoami)" ~/Documents/report.pdf
chmod u+rw ~/Documents/report.pdf

The first line makes you the owner and asks for your password; nothing shows as you type it. The second gives the owner read and write access. For a folder and everything in it, add -R after chown, and use chmod -R u+rwX for the second line. Use the recursive forms only on folders of your own documents.

On an external drive. The simpler fix is to have the Mac disregard ownership there. Select the drive in Finder, choose File, Get Info, unlock Sharing & Permissions, and tick Ignore ownership on this volume. The option appears for Mac-formatted external drives. Drives formatted for Windows do not record owners at all.

Fix the app’s access

  1. Open System Settings, Privacy & Security, Files and Folders. On macOS 12 it is System Preferences, Security & Privacy, Privacy.
  2. Find the app in the list and switch on the place it needs: Desktop Folder, Documents Folder, Downloads Folder, Removable Volumes or Network Volumes.
  3. Quit the app and open it again.

If the app is not listed there, look under Full Disk Access in the same part of Settings, and grant it only to apps you trust.

Two more causes sit on the app side:

  • The file was reached through a list, not chosen by you. Many apps run in a sandbox. They can read a file you pick in their File, Open dialog or drag onto their window, but not always one reached through a link in another document or an old entry in a recent items menu. Open the file through File, Open and the message goes away.
  • The file sits somewhere awkward. An attachment opened straight from an email, or a file inside a disk image or on a read-only share, can be readable by one app and not by the next. Copy it into your Documents folder first. The copy belongs to you, and it opens normally.

What not to do

  • Do not give everyone full access to everything. A recursive chmod 777 across a home folder or a whole drive removes protection from every file it touches. Change the one file or folder that needs it, and leave the System, Library and Applications folders alone.
  • Do not guess when the whole account is affected. If nearly every file in your home folder shows this message, ownership of the entire folder has been changed. Apple documents a reset of home folder permissions that runs from macOS Recovery. Follow Apple’s instructions for your version of macOS, or contact Apple Support.

When access is fixed and the file still will not open

Once the permission is sorted out, a different message sometimes takes its place: the file is damaged, or it is not in a format the app recognizes. That is about the contents, and it is a separate problem. The file someone sent you won’t open works through it step by step.

If it turns out to be a damaged video, PDF or Word document, Manatee has a Repair mode for those. Drop the file onto its menu bar icon or into its window, or right-click it in Finder and choose Services, Fix with Manatee. It reports Fixed, Partial or Not fixable, writes a new copy beside the file, and never modifies the original. Everything runs on the Mac with nothing uploaded. Every feature is free for 24 hours, then it is $9 once.

Manatee lives under the same rules as every other app. It cannot read a file your account is not allowed to read, so fix access first.

Questions

Does this message mean the file is password protected? No. A password-protected PDF or document opens far enough to ask for its password. This message comes from macOS before the app has read anything. If a file does ask for a password you do not have, no permission change will help, and Manatee does not crack passwords either.

Why did this happen to files I copied from my own old Mac? macOS identifies accounts by number, not by name. If your account on the new Mac was given a different number, perhaps because another account was created first, the files still belong to the old number. Making yourself the owner, as shown above, settles it.