Skip to content
MoftgateMoftgate Docs
Product guide

Time Control (Employee Productivity)

Time Control guide: measure application and website time, set productivity rules, and manage work hours, attendance, alerts and reports.

What is Time Control#

Time Control measures how much active time a user spends in each application and on each website. It counts every use as productive, neutral or unproductive by your rules and shows the result as a productivity score.

In this guide: productivity rules, work hours, attendance and privacy.

Overview: today’s status, the work report, the productive share and the hourly breakdown.
Time Control Overview screen
Close image
Product page
For the feature list and licensing, see the Employee Productivity product page .

How it works#

When the module is on, the agent starts a low-privilege sampler in the active user session. The sampler reads the foreground application and idle time every 5 seconds. Sessions go to the server in 60-second batches.

DataWhat is collectedPlatform
Foreground applicationApplication name and file path, every 5 seconds.Windows, macOS, Linux (X11)
WebsiteDomain only. Read from the address bar of Chrome, Edge, Brave, Opera, Vivaldi and Firefox.Windows
Idle timeTime without keyboard or mouse activity. You set the threshold.Windows, macOS, Linux (X11)
Session eventsLogon and screen lock. Used for attendance and locked time.Windows, macOS, Linux (X11)
Not collected
Window titles, screenshots, keystrokes and full URLs are not collected.

Turning on the module#

The module is off by default for each workspace. You need the time_control.update permission to turn it on.

  1. 1
    Turn on the module

    Turn on the Time Control switch on the System > Workspace > Modules tab. You can also use the Settings button at the top right of the Time Control page.

  2. 2
    Set the limits

    Set the idle threshold (60–3600 s), the session retention (1–365 days) and the summary retention.

  3. 3
    Check the notice

    In Agent Profiles > profile > Time Control tab, Notify users about Time Control is on by default.

Changes that need confirmation
Turning the module off or shortening retention asks for confirmation. Every change is written to the audit log.

Productivity rules#

On the Time Control > Productivity rules tab, you make an application or domain productive, neutral or unproductive per endpoint group. A domain rule also covers subdomains. When a device is in more than one group, the strictest class wins.

  • Ready-made catalog: the Add rules wizard lists known global and Turkish applications and websites by category. Picking an item adds its process names on every operating system and its domains.
  • Category rules: classify 31 categories such as Social media, Betting and Development per endpoint group.
  • Apply persona: the Developer, Designer, Sales, Marketing, Finance, Human resources, Support or Executive persona sets a class for every category in one step. The review step shows which existing rules it overwrites.
  • Priority: application and website rules always win over category rules.
Productivity rules: category rules and the Apply persona button.
Category rules screen
Close image
Applications: active time and class per user, device and application.
Applications tab
Close image

Work hours#

On the Time Control > Work hours tab, set a schedule for each endpoint group: working days, start and end hour and time zone. When the end is before the start, the schedule is a night shift.

An hour is in hours when it falls in the window of any group of the device; otherwise it is after hours. Time on devices without a schedule shows as Unscheduled. The Work hours card on the Overview shows these three values and the users with the most after-hours time.

Attendance#

On the Time Control > Attendance tab, each row is a day, user and device: logon, first and last activity, active time and locked time. The status comes from the work schedule of the device group.

StatusMeaning
On timeFirst activity is before the planned start.
LateFirst activity is after the planned start. The delay is shown.
Off dayThe schedule does not cover that day.
No scheduleNo group of the device has a schedule.

Early departure is the time between the last activity and the planned end. When a device is in more than one group, the most flexible schedule is used.

Attendance: daily first and last activity, late arrival and early departure.
Attendance tab
Close image

Timeline and comparison#

On the Time Control > Timeline tab, each row is a user and device pair. Sessions are drawn in the colour of their productivity class. Zoom with the mouse wheel or the slider below the chart.

The Time Control > Compare tab shows two users or two endpoint groups side by side for the same date range: active time, productivity score, focus share, meeting share and after-hours share.

Timeline: sessions per user and device, coloured by productivity class.
Timeline tab
Close image

Alerts#

On the Time Control > Alerts tab, define a rule with a metric and a threshold. Rules are checked every hour against the previous day in the workspace time zone. When there are new alerts, workspace admins get one bell and email notification.

MetricAlert condition
Daily unproductive timeAbove the threshold
Daily after-hours timeAbove the threshold
Daily productivity scoreBelow the threshold. Days with less than 1 hour of activity are skipped.

Privacy#

With the Pseudonymize user names switch on the System > Workspace > Modules tab, every screen, filter, report and alert email shows a stable pseudonym instead of the user name. The key is generated per workspace and never leaves the server. Device names are not hidden.

When monitoring starts, the user sees the notice “This device is monitored by Time Control”. You manage this notice per agent profile.

Confirmation and audit
Turning pseudonymization on or off asks for confirmation and is written to the audit log. When you turn it off, real names return, history included.

Reports#

The Reports > Time Control module includes application and website time, user productivity summary, daily active and idle time, productivity by endpoint group, biggest time sinks and attendance reports. Export them as CSV, XLSX, JSON or PDF, or send them by scheduled email.

You need time_control.view to see the screens and reports, and time_control.update to change settings and rules.

FAQ#

Does Time Control take screenshots or record keystrokes?
No. It does not collect window titles, screenshots, keystrokes or full URLs. For the web, only the domain is stored.
What happens when a device is offline?
The agent writes sessions to a local queue (3 days or 1 GB) and keeps classifying with cached rules. It sends the data when the connection returns.
Does changing a rule change past data?
No. The productivity class comes from the rule in force at the time of use. Categories and work hours are calculated at query time, so they also apply to past usage.
Which platforms have limits?
Linux Wayland is not supported. On macOS and Linux, browsers are measured only as applications, so the Google Meet web version does not appear there. On RDS, only the active interactive session is measured.
How is meeting time measured?
Foreground active time is summed for Zoom, Microsoft Teams, Google Meet and Webex. A call running in the background is not counted.