chmod 750: what it means and when to use it
chmod 750 gives the owner full control and lets group members read or enter, while shutting out every other local user.
750
rwxr-x---
| Who | Digit | Read | Write | Execute |
|---|---|---|---|---|
| Owner | 7 |
Yes | Yes | Yes |
| Group | 5 |
Yes | No | Yes |
| Everyone else | 0 |
No | No | No |
How chmod 750 works
This is the tight sibling of 755 for shared server setups where a web server or worker runs in the same group as the deploy user. The web process can read static files and traverse folders without exposing them to unrelated accounts on the machine.
Setting 750 on a directory lets group members cd into it and list its files, but blocks them from creating, renaming or deleting entries inside.
Where 750 belongs
- Application root directories shared with the web server group
- Internal team scripts meant only for one Unix group
- Home directories on multi-user systems where group reads are permitted
The command
Both of these set exactly the same permissions. The number is shorter; the letters are easier to read back later.
chmod 750 filename
chmod u=rwx,g=rx,o= filename
Check which group the web server actually runs under (such as www-data or nginx) with id before dropping the world bits from 755 to 750.