chgrp

What it does

chgrp ("change group") changes which group owns a file or directory, without touching the user owner or the permission bits. Group ownership matters because Unix permissions grant a separate set of read/write/execute bits to "the group" — changing a file's group changes which set of users that middle permission block applies to.

Beginner examples

• chgrp developers file.txt — change a file's group to developers
• chgrp staff *.log — change the group of every matching log file
• chgrp -R developers /srv/app — recursively change group for a directory tree
• ls -l file.txt — check the current owner and group before/after changing

chgrp developers shared_report.xlsx

Advanced examples

• Recursively update a whole project directory's group after a team reorganization: chgrp -R webteam /var/www/myapp
• Copy the group from an existing, correctly-configured file: chgrp --reference=good_file.txt new_file.txt
• Change the group of a symlink itself rather than its target: chgrp -h groupname symlink
• Combine with find for selective recursive changes: find /srv/app -type f -name "*.log" -exec chgrp appgroup {} \;
• Verify the effect with verbose mode: chgrp -v developers *.conf

find /srv/app -type d -exec chgrp -R webteam {} \;

Common mistakes

• Confusing chgrp with chown and expecting it to also change the file's owner — it only touches the group field.
• Trying to set a group you're not a member of without sufficient privileges and getting a permission-denied error instead of realizing root/sudo is required.
• Forgetting -R when trying to update an entire directory's contents, leaving nested files with the old group.
• Assuming a group change alone grants group members access — the group's permission bits (via chmod) still need to allow the desired access.

Tips

• Use chown user:group file when you need to change both the owner and group at once — it's a single command instead of separate chown and chgrp calls.
• Pair chgrp -R with chmod -R g+rwX when onboarding a new team to a shared directory, so the group not only owns the files but can actually read/write them.
• ls -l shows the group in the second ownership column — always verify with it after running chgrp.

Best practices

• Prefer chown user:group over separate chown/chgrp calls when both need to change, to keep the operation atomic and the intent clear.
• When managing shared team directories, standardize on a dedicated group (e.g. webteam) and apply chgrp -R plus appropriate chmod group bits rather than granting broad "other" permissions.
• Audit group ownership periodically on sensitive directories with find dir -not -group expectedgroup to catch drift.

Real-world use cases

• Handing off a project directory to a different team by recursively changing its group: chgrp -R newteam /srv/project.
• Fixing deployment scripts that create files owned by the wrong group, breaking a shared web server's read access.
• Setting up a shared directory where multiple users in the same group need collaborative read/write access to uploaded files.

Common interview questions

• What's the difference between chgrp and chown? chgrp changes only the group owner; chown can change the user owner, group owner, or both (chown user:group file).
• What permissions do you need to change a file's group? You generally need to own the file and be a member of the target group, or have root/sudo privileges to assign any group.
• How would you recursively change the group of a whole directory? chgrp -R groupname directory/.