Permissions determine who can read, modify or execute a file or traverse a directory. Excessive access may expose data, while overly restrictive settings may stop the site working.

Check before changing

Back up affected files and record current permissions. Identify the correct site directory and owner. Values of 644 for files and 755 for directories are common, but may not suit sensitive files, private directories or special configurations. Do not use 777 to bypass an ownership problem.

Change one item in cPanel

  1. Open Files > File Manager and the site directory.
  2. Select the identified file or directory.
  3. Choose Change Permissions.
  4. Set read, write and execute access for owner, group and others according to the requirement.
  5. Save and test the affected function.

Use Terminal with a precise scope

If you understand Terminal, verify the directory with pwd and inspect the item with ls -l. Adapt these examples only to checked items:

pwd
ls -l ./example.html
chmod 644 ./example.html
chmod 755 ./images

Do not recursively reset the entire home directory. cPanel, mail and application directories require specific permissions. Broad commands can also operate on a wrong path or unrelated items.

Avoid automatic blanket resets

A cron job should not blindly reset permissions across the site every day. Correct the deployment cause and schedule only a necessary, scoped and verified operation. If standard permissions fail, ask support to check ownership and the PHP execution mode.

Interface illustrations

These screenshots show earlier versions. Follow the written instructions and your current account values.

cPanel File Manager
File permission settings in cPanel
Change Permissions command in the File Manager context menu
Read, write and execute checkboxes with permission value 644
Accessing Terminal in the cPanel Advanced section
Command for navigating to public_html in cPanel Terminal
Cron Jobs
Form for adding a cron job in cPanel

Reference documentation