Trevor Williams/DigitalVision via Getty
Follow ZDNET:
Add us as a preferred source on Google.

The `usermod` utility, short for *user modification*, is one of the essential tools in the Linux administrator’s toolkit. As its name openly suggests, this command provides the ability to modify a wide variety of settings and attributes associated with user accounts on a Linux system. For those responsible for managing multiuser environments—from professional system administrators to regular users who want finer control of their accounts—`usermod` proves indispensable. Its versatility allows for modifications ranging from simple descriptive details to more technical refinements, such as changing a user’s primary shell environment or updating group membership. Let us carefully examine the real-world applications of this command, exploring its capabilities one by one.

### 1. Changing user details
When creating a new user through the `adduser` command, you are given the option of inserting various pieces of descriptive information about the account. This includes the full name of the individual, office telephone numbers, home contact details, and even a general comment to distinguish one account from another. However, once an account has been created, altering or supplementing this data cannot be done with `adduser`. Instead, the `usermod` command steps in as the designated tool. For example, if you need to append a distinguishing note—perhaps clarifying which John in the company is which—you could run:
“`
sudo usermod -c “INFORMATION” USER
“`
Here, *INFORMATION* represents the annotation or descriptive text to be stored in the account’s metadata, while *USER* specifies the name of the account in question. This becomes extremely helpful in scenarios where duplicate names occur in a large environment, allowing administrators to prevent confusion quickly.

### 2. Changing a username
Another particularly practical application of `usermod` is altering the login name for a given account. While straightforward, there is one caveat: the process does not automatically alter the associated home directory. For instance, if there is a user account named *sam* and you want to transition that account to *samantha*, the command would be:
“`
sudo usermod -l samantha sam
“`
In this case, the `-l` option stands for *login name*. While the username itself is updated, the user’s personal files remain within the original directory until further changes are executed.

### 3. Renaming a home directory
Following a change in the username, it often makes logical sense to align the home directory naming convention accordingly. However, in order to proceed safely, you must first ensure that the user is thoroughly logged out—otherwise, the process could disrupt data integrity. Once this precaution is observed, you can rename the user’s home directory and simultaneously migrate its content. Using our example, the command would be:
“`
sudo usermod -d /home/samantha -m sam
“`
Here, the `-d` flag specifies the newly intended home directory, while `-m` directs Linux to move existing user files into the newly named folder. Without the `-m` option, the user would log in to an empty environment, which could severely impact their workflow.

### 4. Locking and unlocking a user account
There are circumstances when temporarily suspending access to a user account becomes necessary. For example, the account may belong to a short-term contractor whose project has ended, or even to a child who has temporarily lost computer privileges. The account remains intact but inaccessible. To place such a lock, you would use:
“`
sudo usermod -L USER
“`
When the time comes to restore access, the process is equally simple:
“`
sudo usermod -U USER
“`
Through these two options, administrators can control account access promptly, without resorting to deleting user data or reconstructing the account later.

### 5. Setting an account expiration date
Beyond temporary locking, Linux offers the ability to configure accounts to expire on predetermined dates, a feature invaluable for managing temporary staff or interns. Suppose an employee’s contract ends on October 31, 2025. Instead of relying on memory or manual record keeping, you could automate access removal with:
“`
sudo usermod -e 2025-10-31 USER
“`
The `-e` flag, standing for *expire*, ensures that once the calendar reaches the specified date, the user will no longer be able to log in. This is an elegant solution for preventing forgotten accounts from remaining active after no longer being needed.

### 6. Adding a user to groups
Another frequent task involves group assignments. Many system services, like Docker, require users to belong to specific groups for non-root access. Without proper group membership, ordinary users may be forced to execute commands via `sudo`, creating both inconvenience and potential security issues. By using `usermod`, you can seamlessly add users to one or multiple groups. For instance, to add our original user *sam* to an *editorial* group:
“`
sudo usermod -aG editorial sam
“`
Here, `-aG` works by appending the group membership instead of replacing existing ones. This function is indispensable in collaborative environments where group permissions provide collective access to shared directories or resources.

### 7. Modifying a user’s home directory
At times, renaming a user’s account may leave inconsistency in the filesystem, as their home directory may still reflect the outdated username. The `usermod` command allows an administrator to eliminate this discrepancy. Once again, it is crucial that the user not be logged in during the operation. The command format is:
“`
sudo usermod -d /home/NEWNAME OLDNAME
“`
Where *NEWNAME* signifies the intended directory label, and *OLDNAME* is the user’s current login name. This ensures both organizational clarity and consistency of the system’s structure.

### 8. Changing a user’s shell environment
Although less common, situations arise when adjusting a user’s default shell environment is necessary—maybe to grant access to modern shells like *zsh*, which provide advanced completion features, or to restrict an account to a limited shell. Before modifying the shell, you must confirm its availability by checking the `/etc/shells` file:
“`
cat /etc/shells
“`
If the desired shell is listed, you can apply the change with:
“`
sudo usermod -s /bin/SHELL samantha
“`
The `-s` option explicitly identifies the new shell binary. In practice, this may improve usability or alter the boundaries of a user’s interaction with the system.

—

Through this comprehensive set of features, the `usermod` command proves itself to be far more than a minor administrative helper; it is a multi-purpose instrument that allows Linux administrators to keep user accounts orderly, secure, and tailored to organizational needs.

Sourse: https://www.zdnet.com/article/need-to-modify-user-accounts-in-linux-this-is-the-command-for-you/