Users, Groups and Permissions for DevOps Engineers
Users, groups and permissions are how Linux controls access. Every file has an owner, a group and read, write and execute bits for owner, group and others, shown by ls -l and changed with chmod, chown and chgrp. The sudo command grants limited administrative power, and the root user can do anything.
Stage: Linux · Part of the DevOps Engineer roadmap · Last reviewed 19 November 2026
What to learn in Users, Groups and Permissions
- Read a permission string such as rwxr-x--- correctly
- Change permissions with chmod in numeric and symbolic form
- Change owner and group with chown and chgrp
- Create users and groups and add a user to a group
- Configure sudo access safely using visudo
- Explain setuid, setgid and the sticky bit
Users, Groups and Permissions interview questions
What does chmod 640 do?
It sets read and write for the owner, read for the group and no permissions for others, since 6 is read plus write, 4 is read and 0 is none. It is a common setting for configuration files that contain private values.
Why is the sticky bit set on /tmp?
Everyone can write to /tmp, so without protection users could delete each other's files. The sticky bit allows only a file's owner, the directory owner or root to delete or rename entries, which keeps shared directories safe.
Where Users, Groups and Permissions fits in the DevOps Engineer roadmap
Users, Groups and Permissions belongs to the Linux stage (beginner level). Operating system fundamentals: the Linux course.
Other units in this stage
- Start Here (free)
- Navigating the Filesystem
- Working with Files
- Text Editors
- Text Processing and Pipes
- Processes and Jobs
- Package Management
- The Shell Environment
- Bash Scripting
- Archives, Storage and Filesystems
- Networking and SSH
- Services, Boot and Logs
- Security Basics
- Real Server Admin
- Linux for DevOps
- Capstones and Placement Prep
Back to the full DevOps Engineer roadmap