Community-driven coverage of elementary OS — news, guides & forums
Dark abstract low-poly geometric landscape with layered triangular facets in deep navy, charcoal, and muted teal, illuminated by a soft electric-blue glow near the horizon

News roundups, tutorials, application guides, and forums — built by users, for users of the elegant Linux distribution.

elementary weekly
#20
Latest roundup · 18 Apr 2015
Freya Release
Final
Covered in weekly #19 & #20
Forum Topics
Active
Installation, customization & more

Creating and managing user accounts on elementary OS

An elementary OS computer becomes easier to share when each person signs in with a separate Linux user account. Accounts keep home folders, application settings and access to files apart, so a child’s schoolwork, a family member’s photographs and an adult’s work documents do not have to share one desktop. This separation also makes it possible to restrict administrative changes without restricting ordinary use.

The desktop provides a friendly path for routine account management, while the terminal offers precise control for unusual setups. A sound approach is to retain one tested administrator account, give everyday users standard access, and check that passwords, permissions and recovery options work before handing the computer to another person.

Learn how elementary OS accounts fit together

A local account combines a username, a protected password hash, a unique numeric user ID and a home directory. The login screen uses those credentials to start a session; programs then save most personal settings under the account’s home folder, commonly /home/alex. An online account added through the system menu can synchronise or sign in to particular services, but it is not a replacement for a local Linux user.

elementary OS supports standard and administrative roles. A standard account can run applications, read permitted files and change its own preferences. An administrator can install software, alter system settings and manage other accounts. On Ubuntu-based elementary OS, most administrator power is supplied through the sudo group and the sudo command, which asks for the administrator’s password before making a privileged change.

Keep the account model simple: one accountable administrator and separate standard accounts for daily users. In a shared household, a parent can retain administration while each family member receives an individual login and home directory. Shared wireless passwords may still be known around the house, but separate desktop accounts stop one person from casually opening another person’s saved documents.

Create an account in Settings

Open Settings, choose Users, and select the add-user button, which is commonly shown as a plus sign. An administrator may need to authenticate first. Enter the person’s full name, choose a distinct lowercase username and provide a password. Select the administrative role only when that person genuinely needs to install packages, change the machine or manage accounts. Each user should receive their own credentials rather than sharing an administrator login.

Use names that identify the person without exposing unnecessary personal details. Avoid spaces and characters such as / or : in usernames, because they complicate scripts and file ownership; the full name can contain spaces. A memorable username such as jamie or alex is easier to type on a shared keyboard than a long email address. Check the avatar and automatic-login choices before confirming, especially on a portable computer.

After the account is created, sign into it once to generate its home directory and default configuration. Use the system menu’s Log Out option to finish the administrator session; switching users without saving open work can leave applications behind. Elementary OS applications are usually installed system-wide, so removing an account does not remove an application that other users rely on. A notebook bought through an Australian retailer may arrive with Windows preinstalled rather than Linux. Check whether elementary OS will replace it or share the disk before creating profiles, and back up Windows data before changing partitions.

Add accounts from the terminal

The terminal route is useful for an unattended setup, a classroom image or a server-style installation. Run sudo adduser alex and follow the prompts for the full name, username and password. The password is not echoed while you type it. The adduser command normally creates a home directory, a matching primary group and the default entries for a new local user.

adduser does not grant administrative access by itself. When the role is justified, run sudo usermod -aG sudo alex; the -aG options append the account to the sudo group without replacing its existing supplementary groups. Sign out and back in afterwards, then check with id alex or groups alex. A passwordless sudo configuration is inappropriate for an ordinary desktop unless there is a deliberate, documented security reason.

Use getent passwd alex to confirm the account exists and ls -ld /home/alex to check its home directory. The command passwd alex lets the user change their own password, while an administrator can use sudo passwd alex. Avoid editing /etc/passwd, /etc/shadow or /etc/group in a text editor: those files have strict formats, and user-management tools apply the required ownership and permissions safely.

Grant only the permissions people need

Administrative access is valuable because it can read private data, change security settings and run commands as root. Standard access is enough for web browsing, documents, music and normal application use. Give a user administrator rights for a defined need, then review that membership later. Do not remove the last administrator from the sudo group, and do not remove your own membership until another administrator has successfully signed in.

For a shared project folder, use a group rather than making everything world-writable. For example, run sudo groupadd study, add each participant with sudo usermod -aG study USERNAME, then prepare the directory with sudo mkdir -p /srv/study, sudo chown root:study /srv/study and sudo chmod 2770 /srv/study. Avoid chmod 777, which lets every account on the computer change files. Group permissions still depend on the folder’s parent permissions and on whether the applications involved honour the Unix ownership model.

Audit membership with id USERNAME and groups USERNAME. To withdraw administrator access, run sudo gpasswd -d alex sudo from another administrator session, then check the result. A service account used by a backup tool or print server is another category of user: it should not be given interactive administrator privileges merely because it needs to write to a particular directory.

Control passwords, locks and expiry

Change an account password through Users in Settings or with passwd in a terminal. Encourage a long, unique passphrase rather than a short password built from a name and birth year. A password manager can generate and store one, but keep the local account password distinct from reused website credentials. Saved browser passwords do not automatically unlock an encrypted home directory.

Locking and expiry serve different purposes. sudo passwd -l alex locks the password without deleting the account; sudo passwd -u alex unlocks it. sudo chage -M 90 alex sets a maximum password age of 90 days, while sudo chage -i 7 alex sets a seven-day inactivity period after password expiry. Use sudo chage -l alex to inspect the current settings. An administrator should explain any expiry policy so a user is not locked out during an assessment or while travelling.

Automatic login is convenient on a single-owner desktop but unsuitable for a shared or portable computer. Disable it in the Users settings and use the screen-lock controls to lock an unattended session. Most Australian states change their clocks twice a year, so verify automatic time synchronisation and the correct IANA time zone for your city before relying on exact expiry dates. Locking the screen and logging out are separate actions, and both should be part of a shared-device routine.

Maintain accounts on shared computers

A family notebook in Sydney, a school-managed laptop in Brisbane and a public library workstation each call for a different level of caution. At school, ask the technology team before creating accounts or changing permissions; the device may already join a managed network. A library workstation may offer only a temporary session, and saving files to a personal USB drive might be forbidden. Follow the site’s policy rather than bypassing it.

Back up each person’s home directory to an approved external drive or network location before changing accounts, reinstalling the system or replacing the disk. Removing an account through Users may offer to delete personal files, and the command sudo userdel alex normally leaves /home/alex in place, whereas sudo userdel -r alex requests removal of the home directory and related files. Confirm the backup and check the account’s ownership before choosing either form of deletion.

For an Australian business or community organisation, the Privacy Act 1988 and the Australian Privacy Principles may apply to personal information handled through its systems. Unique accounts, limited access, secure credentials and records of who administers the machine support the security and accountability expectations in principles such as APP 3, APP 5, APP 6 and APP 11. Local Linux accounts alone do not determine legal compliance, but they provide a practical foundation for controlled access.

Keep recovery and maintenance habits

Losing administrator access is often a recovery problem rather than a reason to reinstall elementary OS. Before changing administrator membership, record which accounts belong to the sudo group and keep one existing session open until a new administrator has signed in successfully. For remote help, agree on a time window and use a reputable service with the administrator present; do not send an administrative password through ordinary chat.

If the graphical login fails, try a text terminal such as Ctrl+Alt+F3, where available, and sign in as an existing administrator. Reset the affected password with sudo passwd alex. This cannot bypass full-disk or home-directory encryption: if that encryption key is lost, the recovery key is required. Test the recovery route while the machine is working, and store any recovery key according to the organisation’s or household’s security procedure.

Before deleting or renaming an account, back up its data and record its user ID, group and supplementary memberships. Renaming can leave file ownership and application settings referring to the old name. Creating a replacement standard account and copying selected documents is often less disruptive than trying to preserve every old configuration. For a second reference, this account configuration guide may help when a menu differs between elementary OS releases.

The account model worth remembering is simple: one trusted administrator, separate standard users, and a recovery path that has been tested rather than assumed. Strong passwords, restrained privileges and retained backups protect both privacy and everyday usability on elementary OS.

Browse the News Archive
Latest Updates

From the elementary weekly series

Low-poly faceted abstract render in dark charcoal and electric blue tones, suggesting a news bulletin or announcement
elementary news

elementary weekly #20

The first week with the final Freya release — community reactions, tips, and early impressions gathered in one roundup.

Abstract low-poly geometric scene in midnight blue and soft cyan, conveying a live broadcast or event atmosphere
elementary news

elementary SPECIAL

A live Hangouts event with the elementary OS founders, held on 11 April 2015, discussing the Freya final release.

Low-poly faceted render in deep navy and muted teal with subtle amber highlights, suggesting a tutorial or guide
Tips and Tricks

Timeshift Guide

How to use Timeshift — the intuitive system restore utility for elementary OS — to recover from configuration mishaps.

Explore

Topics & Resources

Dive into guides, application recommendations, and community discussions covering every aspect of elementary OS.