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

Automatic Screen Time And Parental Controls On Elementary OS

A shared computer can be useful for homework, creative projects, communication, and entertainment, but unrestricted access can quickly become difficult to manage. elementary OS does not provide a single built-in dashboard that combines daily screen-time limits, website filtering, application blocking, and activity reports. However, several Linux tools can be combined to create a practical family setup.

The most reliable approach is to separate everyday accounts from administrative control. A child should use a standard user account, while the parent keeps the administrator password private. This prevents changes to time limits, installed software, network settings, and system policies.

Screen-time management on elementary OS usually involves three layers: scheduled login restrictions, application and website controls, and household rules that support the technical limits. The setup below focuses on tools that work with the Ubuntu-based foundation of elementary OS and can be adjusted as your family’s needs change.

Create A Separate Child Account

Start by creating a dedicated standard account for each child. Open System Settings and look for the user or account management panel. Select the option to add a user, choose a normal or standard account type, and assign a strong password that the child does not know. Use a recognizable account name, such as “Alex,” rather than sharing the parent’s profile.

A separate account protects personal files and makes parental controls much easier to apply. Browser history, downloaded files, application preferences, and desktop settings remain isolated from the parent’s account. It also means that scheduled restrictions can target one user without interrupting the parent’s work.

The parent’s account should retain administrator privileges, but daily browsing should happen from the standard account whenever possible. Avoid giving the child access to administrative authentication prompts. If an application needs installation or a system component needs updating, handle that task from the administrator account.

Test the new account before applying restrictions. Sign in, open the applications the child needs, connect to the home network, and check that documents can be saved. This catches permission problems early and gives you a clean baseline for troubleshooting.

Choose A Time Management Tool

For automatic daily limits, Timekpr-nExT is one of the more suitable Linux utilities. It can restrict when a user may log in, set the number of minutes available per day, and define permitted hours. Depending on the package version and desktop integration, it may log the user out or prevent further access when the allowance expires.

Install it from a trusted software source compatible with your elementary OS release. Some releases may require adding a repository or downloading a package manually, so check the project’s documentation before installing. Avoid random scripts that promise “parental controls” without showing their source or explaining what system files they modify.

After installation, open the administrator interface and select the child’s account. Configure a schedule that reflects the family routine. For example, you might allow access after school, block the account during dinner, and set a shorter allowance on school nights. A separate weekend schedule can provide additional flexibility without removing the daily limit.

Use a conservative setting at first and observe how it behaves. Linux time-control tools may rely on background services, session monitoring, or logout actions. Test a short limit while the child is present, then verify that the restriction resets at the expected time. Check whether unsaved work is handled safely before trusting automatic logout for important school assignments.

Configure Scheduled Access Carefully

A screen-time limit and a permitted login schedule solve different problems. A daily allowance controls total usage, while a schedule controls when usage may begin or end. Combining both gives you greater control. A child could receive two hours per day but use those hours only between 3 p.m. and 8 p.m., for example.

Keep essential access separate from leisure access. If the computer is used for schoolwork, avoid setting a blanket shutdown during periods when assignments are likely. Instead, create a predictable study window and discuss how entertainment applications fit within the remaining allowance. A strict timer that interrupts homework can encourage workarounds and create unnecessary conflict.

Time zones, daylight-saving changes, and system clock adjustments can affect scheduled controls. Make sure the computer’s date, time, and time zone are correct. Do not allow the child to change the clock, because altering system time can interfere with timer-based restrictions. The administrator account should be required for changes to date and time settings.

A scheduled shutdown is another option, but it is less precise than a user-focused time-management service. A command scheduled through systemd or the desktop’s power settings can turn off the entire computer at night, but it also interrupts the parent’s session and may cause data loss. Use whole-device shutdown only when the computer is dedicated to children or sits in a shared room with a clear household bedtime.

Add Application And Website Controls

Time limits do not determine what a child can do during the allowed period. Review the installed applications from the child’s account and remove programs that are unnecessary or unsuitable. Keep the application set small, especially on a first computer. A focused selection of educational software, a browser, a document editor, and creative tools is easier to supervise.

For trustworthy software discovery and installation guidance, browse the elementary OS application guides. This can help you identify programs that fit the desktop environment without installing unverified packages from questionable websites.

Browser-level controls are useful for blocking adult content, gambling, malware, and known distracting services. Family-safe DNS providers can filter traffic for every device on the home network, while browser extensions can apply additional rules to one profile. DNS filtering is easier to maintain centrally, but it may not distinguish reliably between different users if the child takes the computer elsewhere.

For stronger control, configure filtering at the router and use a separate child browser profile. Keep the parent’s browser profile protected by a password or operating-system account separation. Remember that DNS filters generally block domains rather than individual pages, and they cannot replace supervision for messaging platforms, social networks, or video services.

Application restrictions require more care than removing icons from the application menu. A child may still launch a program from the file manager, a command line, or a downloaded copy. Standard-user permissions reduce many risks, but they are not a complete application sandbox. When a particular program must be unavailable, uninstall it or use a dedicated application-control mechanism supported by your release.

Compare Common Control Methods

Each method covers a different part of family computer management. A timer is effective for duration and routine, a filtered network is effective for broad categories of websites, and account separation is effective for protecting settings and files. Combining modest controls is usually more dependable than expecting one package to solve every problem.

The following comparison can help you decide where to begin:

Method Main purpose Strengths Limitations
Standard user account Protect system settings and files Simple, built into the operating system, easy to maintain Does not set time or content limits
Timekpr-nExT Daily usage and login schedules Supports automatic limits for a selected user Requires testing and administrator configuration
Family-safe DNS Website and category filtering Covers browsers and many applications on the home network Less effective away from home; can overblock
Browser family profile Safer web browsing Allows browser-specific restrictions and history review Applies only to that browser
Router schedule Network access windows Controls internet availability for connected devices Does not stop offline applications
Manual rules Household expectations Flexible and easy to explain Depends on consistency and supervision

Begin with the standard account and a predictable schedule, then add network filtering if web access is the main concern. Installing several overlapping control systems at once can make troubleshooting difficult. When something is blocked unexpectedly, you should be able to identify which layer caused it.

Protect The Controls From Workarounds

Parental controls are only useful when the protected settings cannot be changed easily. Use a long administrator password and do not save it in the child’s browser or password manager. Lock the parent’s session whenever stepping away from the computer, and configure automatic screen locking after a short period of inactivity.

Review boot and recovery security as well. Someone with physical access may attempt to boot a live Linux USB, change files offline, or reset an account password. If the computer contains sensitive family information, enable full-disk encryption during installation when practical. Set a firmware password and prevent unauthorized external booting if the device’s firmware supports those options.

These measures should be balanced with the need for recovery. Keep a secure record of the administrator credentials and know how to access recovery tools if the timer service fails. Before major operating-system upgrades, temporarily document the current settings and verify that the parental-control package supports the new release.

Privacy deserves attention as well. Avoid installing monitoring software that captures every keystroke, records personal messages, or uploads browsing data without a clear reason. A daily limit, safe browsing filter, and visible household agreement are often enough for younger users. Older children may benefit more from transparent rules and periodic conversations than from hidden surveillance.

Make The Routine Predictable

Automatic limits work best when the child knows what will happen. Explain the permitted hours, the daily allowance, and the warning behavior before the controls take effect. If the computer logs out at a fixed time, establish a reminder several minutes beforehand so schoolwork can be saved and applications can close normally.

Use separate expectations for different activities. Homework, accessibility tools, reading, and creative work may deserve different treatment from games or entertainment. Linux time-management utilities may not classify applications by purpose, so a family agreement can supply the distinction that the software lacks.

Review the configuration every few weeks. School holidays, exam periods, changing bedtimes, and new responsibilities may require a different schedule. Check the child’s account for unfamiliar applications, browser extensions, and downloaded files, but explain the review rather than making it feel like secret inspection.

Practical recommendations for a dependable setup include:

  • Use one standard account per child and keep administrator credentials private.
  • Combine a daily time allowance with permitted login hours rather than relying on one limit.
  • Test automatic logout and short trial schedules before using them for important assignments.
  • Add family-safe DNS or router filtering when unsuitable websites are the primary concern.
  • Explain the rules clearly and review them as the child’s age and routine change.

Maintain And Troubleshoot The Setup

After installing a time-management service, check that its background process starts automatically after reboot. Confirm the child’s account is selected, the schedule uses the correct time zone, and the service remains active after system updates. If restrictions stop working, inspect the application’s logs or service status from the administrator account instead of repeatedly changing settings.

A common problem is confusing a locked session with a completed daily allowance. Screen locking protects an active session, but it does not necessarily count usage or prevent the child from signing back in. Likewise, a router schedule can cut off internet access while leaving offline games and downloaded videos available. Identify the exact behavior you need before choosing a control.

Updates can also replace configuration files or disable third-party integrations. Keep a note of the package name, repository, configuration values, and installation method. After upgrading elementary OS, test the child account, browser filter, network access, and timer independently. Do not assume that a previously working parental-control system survived a major release unchanged.

If a tool becomes unreliable, simplify the arrangement. A standard account, a consistent household schedule, and a router-level filter are preferable to a complicated setup that nobody can maintain. Reliable boundaries matter more than having a long list of technical restrictions.

Set up the controls while logged in as the administrator, run a short test with the child account, and confirm each limit behaves as intended. Then make the schedule part of the household routine and revisit it regularly. Explore the elementary OS software ecosystem, document your working configuration, and share practical fixes with the community so other families can build a safer, calmer computer experience.

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.