Double-clicking an application bundle on macOS only to be confronted with the alert dialogue: ‘You do not have permission to open the application. Contact your computer’s administrator or your organization for assistance’ is a frequent frustration for Mac users. This permission stoppage occurs across freshly downloaded utilities, migrated applications, and legacy developer binaries. Rather than indicating an actual lack of administrative authority, this error message is typically triggered by missing executable execution bits (POSIX permissions), quarantined Gatekeeper security attributes, or architecture mismatches on modern Apple Silicon Macs.
Why macOS Denies Permission to Launch Applications
Apple’s stringent security architecture evaluates file permissions and digital notarisation before spawning process threads. Common failure triggers include:
- Stripped Executable Execution Bits: When apps are downloaded inside raw zip archives or unarchived using third-party extractors, the primary binary inside
Contents/MacOS/can lose its POSIX executable flag (+x). - Gatekeeper Extended Quarantine Flags: macOS tags web-downloaded binaries with the
com.apple.quarantinemetadata flag. If notarisation checks fail or unsigned code is detected, macOS masks the security alert behind a generic permission error. - Corrupted Access Control Lists (ACLs): File-level permissions inside your local user library or Applications directory improperly restricting read access.
- Universal Binary Architecture Discrepancies: Attempting to run Intel x86_64 binaries on Apple Silicon (M1/M2/M3/M4) Macs without the Rosetta 2 translation environment installed.
Step 1: Restore Executable Permissions via Terminal
The most common underlying cause is that the underlying Unix binary inside the .app wrapper lacks executable execution rights.
- Open the Terminal application (found in Applications > Utilities).
- Execute the
chmodcommand to restore executable permissions to the binary inside the application bundle:chmod +x /Applications/YourApp.app/Contents/MacOS/* - Replace
YourApp.appwith the exact filename of your application (or drag the application bundle directly into Terminal to automatically populate its path). - Press Enter. If prompted, enter your macOS user login password to authorise the command.
- Double-click the application in Finder to test launching.
Step 2: Remove the Gatekeeper Extended Quarantine Attribute
If the application was downloaded from outside the Mac App Store, removing the extended quarantine attribute bypasses the false permission dialogue.
- In Terminal, check if the app possesses an active quarantine flag:
xattr -l /Applications/YourApp.app - If the output displays
com.apple.quarantine, strip the attribute recursively:sudo xattr -rd com.apple.quarantine /Applications/YourApp.app - Press Enter and authenticate with your administrator password.
- Launch the app again. macOS will now recognise the package as trusted.
Step 3: Verify and Install Rosetta 2 (Apple Silicon Macs)
If you are attempting to launch an Intel-based application on a Mac powered by an Apple Silicon processor, missing Rosetta 2 binaries prevent execution.
- Open Terminal and execute the following command to download and install Rosetta 2:
softwareupdate --install-rosetta --agree-to-license - Wait for the package download and verification process to finish.
- Once complete, locate the application in Finder, right-click it, and select Get Info.
- If available, check the box labelled Open using Rosetta.
- Launch the application to verify operational status.
Step 4: Repair User Account File Ownership and ACLs
If the application bundle was installed into your user home directory (~/Applications) under an alternate user identifier, reset file ownership.
- Execute the following ownership reset command in Terminal:
sudo chown -R $(whoami) /Applications/YourApp.app - Ensure read and execute permissions are set across all child directories:
chmod -R 755 /Applications/YourApp.app - Close Terminal and open the application normally from Launchpad or Finder.