JustUtils
shield_lockLinux permissions 路 explained as you click

Chmod 700 Explained & Calculator

Understand chmod 700 for private folders and scripts, check the access it grants, and generate a ready-to-paste command.

STEP 1

What are you changing?

Execute means different things for a file and a directory.

For a directory: Read lists names, Write adds or removes items, and Execute lets someone enter the directory and reach items inside.

STEP 2

Choose access

Owner permissions

Owner

digit 17

rwx

Usually you or the account that created it.

Group permissions

Group

digit 20

---

Accounts collected in the file's owning group.

Everyone else permissions

Everyone else

digit 30

---

Any other account on the same system.

YOUR RESULT

700rwx------

u=rwx,g=,o=

Owner

Can list names, add or remove items, enter

Group

Can no access

Everyone else

Can no access

THE PART MOST CALCULATORS SKIP

See what will actually change

Find the numeric mode with stat -c '%a' path on Linux, then review each permission being added or removed.

644arrow_forward700
addOwner: executeremoveGroup: readremoveEveryone else: read

TOP 5 EVERYDAY MODES

Start from the job, not the digits

Each common mode has its own explainer page and loads directly into this calculator. Pick the situation that sounds like yours, then check the access before copying.

CHMOD IN ONE MINUTE

What is chmod?

Every Linux file carries a tiny access list. chmod is the command that rewrites that list. It does not move the file, change its contents, or choose its owner鈥攊t only changes what the owner, group, and everyone else are allowed to do.

Think of the three digits as three keycards. The first card belongs to the owner, the second to the group, and the third to everyone else. Each card gets points for Read (4), Write (2), and Execute (1). Add the allowed actions to get that card's digit.

The only math you need

4Read+2Write+1Execute=7all three
Why 777 is not a universal fix: it hands every keycard every permission. Fix ownership or choose the smallest access that solves the real need instead.

DIGIT 1u

Owner

Usually you or the account that created it.

DIGIT 2g

Group

Accounts collected in the file's owning group.

DIGIT 3o

Everyone else

Any other account on the same system.

Chmod 700 in practice

How to decide whether 700 fits your directory

Mode 700 grants read, write, and execute permission to the owner and nothing to the group or everyone else. For a directory, the owner can list it, enter it, and manage entries while other local accounts are blocked by these basic mode bits.

Owner
7 = read + write + execute
The owner can list the directory, enter it, and create, rename, or remove entries.
Group
0 = no access
Even members of the owning group cannot traverse or list the directory.
Everyone else
0 = no access
Other local accounts receive no directory access through the standard mode bits.

A practical example

A private directory containing deployment credentials

A deploy account may keep short-lived credential files and helper configuration under one private directory. Mode 700 prevents other ordinary accounts from listing names or traversing into that directory, while leaving the owner able to maintain its contents.

Before saving the change

  • Confirm that no service running as another account needs to read the directory.
  • Inspect the files inside; directory privacy does not make overly broad file modes a good default.
  • Check for ACLs that may grant access beyond the three displayed permission classes.

Common mistake to avoid

If a service runs under a different user, mode 700 can break it immediately even when the service previously read only one file inside the directory.

When to choose something else

Choose 750 when a controlled group needs read and traversal access. Use ACLs when one additional service account needs access but broad group membership would be inappropriate.