HR module pitfalls

Step by step

Check who can approve one employee's request

The manager entered in the employee record decides, not the module permission.

1. Open HR → Employees, find the employee, and click Edit.
2. Check Manager. This is the person who will receive the request for a decision.
3. If this field is empty, no one except a company administrator can approve the request. The system says this directly when it is submitted, instead of quietly saving a request that cannot be reviewed.
4. No one can approve their own request, even an administrator or someone listed as their own manager.

A company administrator can review any request. This is a safeguard if the manager has left or was never assigned (Leave requests — workflow and allowance).

Correct a leave allowance

The allowance is no longer stored as a number that must be corrected manually. Remaining days are calculated from the annual allowance minus days reserved by pending and approved requests. Cancelling a request returns the days automatically.

1. Go to HR → Employees and click Edit beside the person.
2. Change Annual leave days, the allowance. The current balance is recalculated automatically.
3. Click Save.

Check whether reports have data to work with

1. Open Advanced → Event log. Set From and To to the date you want and check for clock-ins in Date and time, Employee, Event type, Source, and Kiosk.
2. Check that the employee has an employee record in the company (HR → Employees). A clock-in without a record cannot be used to build a workday. The event is saved and a warning is logged, but no workday is created.
3. If there is a record but still no workday, ask the person who manages the deployment to recalculate the date range. There is no interface button; there is an API action (POST /api/attendance/records/recalculate/) and a nightly task that closes days up to two days old. Recalculation is idempotent, so you can repeat it without creating duplicate workdays.

1. Workdays are generated automatically, but depend on the task queue

Every clock-in queues a workday rebuild in the background. If the queue broker is unavailable, rebuilding happens immediately in the same request. The workday is never lost, but clocking in takes longer.

Workdays are closed automatically, and the system analyzes compliance and anomalies. If the analysis stops updating, contact NOXTI support; having a workday does not prove the analysis ran (Event log, corrections, and workdays).

2. A night shift belongs to the day it started

A 22:00–06:00 shift is one workday, the day the employee clocked in, not the two calendar days it touches. Filters and reports set to “yesterday” show it on its start date.

3. Self-service does not require module permission

Clocking in and out from the panel and viewing your own attendance require only a sign-in and an employee record. Attendance permission is not needed.

Leave requests are the exception: they require module permission, even for your own requests. This inconsistency can be surprising when assigning roles to regular employees.

4. The kiosk screen requires warehouse permission

The kiosk URL inside the system is protected by Warehouse and returns, not Attendance permission. Someone with only HR permissions cannot open it.

Separate public kiosk URLs work without signing in, as intended (Kiosk and time clocking).

5. Two reports require warehouse permission

Employee productivity (HR) and Work time utilization require permission for WMS Picking reports. A role limited to HR will see two fewer items in the reports group (HR reports and payroll system exports).

In the role window, open Field permissions, expand the Report group, and check Read for WMS - Picking Performance.

6. The event log is under Advanced

It is not in HR. You will not find clock-ins by looking under HR. Access requires both Advanced (IT / diagnostics) and Attendance; granting only the first reveals nothing (HR and time tracking — what the module includes).

7. Changing kiosk configuration requires 2FA confirmation

Configuring kiosks, event types, and login methods, as well as issuing an employee a QR code or PIN, requires renewed identity confirmation (step-up 2FA). The 2FA verification required window appears; enter the code and confirm.

You do not need confirmation just to view these settings. Schedules and schedule groups are ordinary HR settings and do not ask for 2FA (Employees and schedules).

8. A QR code is shown only once

After it is generated, the code appears in the window where it was created. Print or save it immediately. Later, the system can confirm only that the code exists and when it was created; it cannot show the code again. If it is lost, generate a new one, which invalidates the old code.

Small details

• Review the missing clock-out flag on workdays regularly. The nightly job marks such days but does not guess a clock-out time. Without correction, the day will not be calculated properly.
• Leave is counted in working days; weekends and public holidays do not use up the allowance (Leave requests — workflow and allowance).
• The mobile and import sources exist in the data model, but no path for them was found in the system. Treat them as a possibility, not a working feature.
• Old HR screen addresses redirect, so saved bookmarks still work.