On macOS Mojave, permission issues can cause apps to misbehave, slow performance, or prevent access to system resources. This guide explains what file and folder permissions are, how to recognize common symptoms, and how to repair permissions using Disk First Aid and the command line. It is intended as an evergreen reference for both technical and non-technical users who need reliable, safe steps to diagnose and fix permission problems.
Understanding File and Folder Permissions
Permissions control which user accounts and system processes can read, write, or execute files and folders on a Mac. macOS uses a combination of POSIX permissions, access control lists (ACLs), and extended attributes to enforce these rules. Each file or folder has an owner, a group, and a set of permission bits that define allowed actions for the owner, group members, and everyone else. System processes typically run under special system identities, while user apps run under your user account or under sandboxed identities.
Core Permission Concepts
- Owner: The user or system entity that created the item, usually granted broader rights.
- Group: A set of users who share specified access rights.
- Others: All other users on the system.
- Read: Ability to view contents or metadata.
- Write: Ability to modify or delete contents and metadata.
- Execute: Ability to run a file as code or traverse a folder.
macOS also relies on the system integrity protections Apple introduced, including System Integrity Protection (SIP), which limits what even privileged users can modify in protected parts of the system volume. Understanding these mechanisms helps you interpret permission problems and choose appropriate repair strategies without compromising security.
Common Symptoms of Permission Issues
Permission problems often appear gradually and can be mistaken for application bugs or hardware issues. Typical signs include apps that fail to launch or update, unexpected authentication prompts, or error messages about access being denied. You might notice items in your Home folder or on the Desktop that cannot be opened, copied, or deleted. System-level symptoms can include slow startup, menus or preferences not saving, and inconsistent behavior across user accounts.
When to Suspect Permissions
- An app worked after an update and then stopped.
- You see error codes referencing EACCES, EPERM, or 'Operation not permitted'.
- Items on your Desktop or Documents behave oddly after installing third‑party software.
- Multiple user accounts on the same Mac experience similar issues.
Note that many modern errors, especially on Apple silicon Macs, are related to SIP and not classic permissions. Exact error messages and the paths mentioned in logs are valuable clues for diagnosing whether permissions, SIP, or another factor is the root cause.
How macOS Mojave Stores Permissions
macOS Mojave stores basic POSIX permissions in the volume metadata and extended attributes for more nuanced controls, such as quarantine attributes and user access tags. These attributes are applied to files and folders below key locations, including the system volume, user home folders, and application bundles.
| Item | Verified Detail | Source Type |
|---|---|---|
| Permission Model | POSIX with ACLs and extended attributes | Apple Developer Documentation, macOS Internals |
| Protected Locations | /System, /usr, /bin, /sbin, /private | Apple SIP documentation |
| Common Error Codes | EACCES, EPERM, -61 (paramErr) | Apple man pages, system logs |
| Diagnostic Tools | Disk First Aid, Console, chmod, chown | Apple support resources, macOS manuals |
Using Disk First Aid to Repair Permissions
Disk First Aid in macOS Mojave provides a graphical way to verify and repair permissions on your startup disk and other volumes. It checks the internal metadata and attempts to restore expected permissions for system and user locations without requiring manual intervention.
Step-by-Step Disk First Aid Workflow
- Open Disk Utility, located in /Applications/Utilities/.
- Select the volume you want to repair, typically your startup disk.
- Click First Aid, then confirm the operation.
- Review the results; if repairs were made, restart your Mac to ensure changes take effect.
Disk First Aid is most effective on the volume that contains your system files. If it reports no issues but you still suspect permission problems, consider checking external drives or Time Machine backups for inconsistencies.
Repairing Permissions with the Command Line
For advanced users and scripts, the command line offers precise control over permissions. Standard utilities such as chmod, chown, and dscl allow you to inspect and modify access rights at the file and directory level. The following procedures assume you are comfortable entering commands in Terminal and understand the risks of modifying system files.
Verification and Repair Steps
- Open Terminal in /Applications/Utilities/.
- List current permissions with
ls -ld <path>to confirm the issue. - Repair permissions on your user home directory using
sudo chmod -R u+rw ~/, where appropriate. - Reset application-specific items in ~/Library/Containers and ~/Library/Application Support if needed.
Prefer built-in tools over custom scripts when possible. For system directories, combine sudo with extreme caution, and always back up important data before applying broad permission changes.
When Not to Repair Permissions
Not all issues are solved by repairing permissions. System Integrity Protection (SIP) protects critical system files on macOS Mojave, and changes to those paths may be reverted or blocked. If First Aid and command‑line repairs fail or produce errors about protected resources, consult Apple support or consider reinstalling the affected app or macOS itself as a safer option.
Decision Checklist
- Does the error message reference a path under /System or /usr? Likely SIP related.
- Does the issue persist after repairing permissions and restarting? Consider reinstalling the app or macOS.
- Are you on Apple silicon? SIP behavior and repair steps can differ from Intel-based Macs.
Preventing Future Permission Problems
Reduce the likelihood of permission issues by managing software installations carefully, avoiding manual edits to system files, and keeping your Mac updated. Use App Store and verified installers when possible, and limit the use of sudo and chmod to situations you understand. Regular backups, both local and cloud-based, provide an additional safety net if repairs require restoring files.
Periodic checks using Disk First Aid can catch subtle inconsistencies before they affect daily use. If you frequently install third‑party utilities or manage multiple user accounts, consider documenting expected permission states for critical locations so you can compare them quickly during troubleshooting.