How to Fix ‘You Do Not Have Permission to Open the Application’ on Mac

Double-clicking an application in your Mac's Applications folder or attempting to launch software downloaded from the web only to be blocked by an alert dialogue stating “You do not have permission to open the application. Contact your computer or network administrator for assistance” severs access to essential tools. In macOS, application execution is governed by rigorous UNIX-level POSIX file permissions, Gatekeeper quarantine attributes, and Apple security architecture (including Code Signing, Notarization, and System Integrity Protection). When an application binary loses its POSIX execution bit (+x), Gatekeeper applies an unresolvable quarantine flag, or an Intel-compiled binary lacks Rosetta 2 translation on Apple Silicon (M1/M2/M3/M4), macOS refuses to execute the binary. This technical guide outlines how macOS application permissions operate and provides practical methods to restore application access.

Why Does macOS Report ‘You Do Not Have Permission to Open the Application’?

The macOS kernel and launch services subsystem verify multiple cryptographic and filesystem criteria before spawning an application process. Common causes of permission blocks include:

  • Missing POSIX Execute Permissions: The primary executable binary located inside the application bundle (App.app/Contents/MacOS/binary) lacking the UNIX executable flag (chmod +x).
  • Gatekeeper Quarantine Attribute Lock: macOS applying the com.apple.quarantine extended attribute to internet downloads, blocking unsigned or notarization-failed apps.
  • Corrupted Code Signature: An application bundle modified during download or unarchiving, causing Apple's security daemon to reject the binary signature.
  • Architecture Incompatibility: Attempting to run a legacy x86_64 Intel application on an Apple Silicon Mac where the Rosetta 2 dynamic binary translator is uninstalled or damaged.
  • Corrupted Launch Services Database: The macOS Launch Services registry holding stale permissions mappings for the application identifier.

Method 1: Grant POSIX Executable Permissions Using Terminal (chmod +x)

The most common cause of this error is the internal binary missing execute permissions following an unarchiving error.

  1. Open Terminal on your Mac (press Command + Space, type Terminal, and press Enter).
  2. Type the following command followed by a space (do not press Enter yet):
    chmod +x 
  3. Open Finder and navigate to your Applications folder.
  4. Right-click on the problematic application and select Show Package Contents.
  5. Open the Contents folder, then open the MacOS folder.
  6. Inside the MacOS folder, you will see the main UNIX executable file (it often carries a dark square terminal icon).
  7. Drag and drop this executable file directly from Finder into your Terminal window to automatically populate its exact file path.
  8. The full command will resemble:
    chmod +x /Applications/AppName.app/Contents/MacOS/AppName
  9. Press Enter in Terminal.
  10. Attempt to launch the application normally from Finder.

Method 2: Remove the Gatekeeper Quarantine Extended Attribute

Clearing the quarantine metadata flag removes Gatekeeper's restriction on downloaded software packages.

  1. In Terminal, execute the xattr command with the recursive and delete flags:
    sudo xattr -rd com.apple.quarantine /Applications/AppName.app
  2. Replace /Applications/AppName.app with the actual path to your application (or simply drag the app icon from Applications into Terminal).
  3. Enter your macOS administrator password when prompted and press Enter.
  4. Launch the application again.

Method 3: Install or Update Rosetta 2 on Apple Silicon Macs

If your Mac is equipped with an Apple Silicon chip (M1, M2, M3, or M4) and you are attempting to run an Intel app, Rosetta 2 is required.

  1. Open Terminal.
  2. Execute the automated Rosetta installation command:
    softwareupdate --install-rosetta --agree-to-license
  3. Wait for the download and package verification to complete.
  4. Once installed, right-click the application in Finder, select Get Info, and check the box labelled Open using Rosetta if available.
  5. Double-click the app to launch it.

Method 4: Re-Sign the Application Locally Using codesign

If an ad-hoc or open-source application has a broken code signature, applying a local ad-hoc signature authorizes execution.

  1. In Terminal, execute the following command:
    sudo codesign --force --deep --sign - /Applications/AppName.app
  2. Press Enter and enter your password.
  3. This command signs the application bundle locally with an ad-hoc certificate, satisfying macOS code integrity checks.

Method 5: Reset the macOS Launch Services Database

Rebuilding the Launch Services registry resolves corrupt file associations and application registration tokens.

  1. In Terminal, execute the Launch Services rebuild command:
    /System/Library/Frameworks/CoreServices.framework/Frameworks/LaunchServices.framework/Support/lsregister -kill -r -domain local -domain system -domain user
  2. Wait for the command prompt to return, then restart the Finder process:
    killall Finder
  3. Reboot your Mac and attempt to launch the software.

For more Apple operating system tutorials and security troubleshooting guides, explore our Digitash macOS archive.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.