InnerWeb
Skip to main content

GDPR in working time records: absences and access rights

A sick-leave code is health information, so it should not be visible to everyone who approves working time. The supervisor needs to know that an absence is justified, not why. Below is a practical split of roles and the settings that implement it.

3
roles with access to the sick-leave code: employee, HR, administrator
Source: working time module documentation

Why the reason for an absence requires care

Information about a sick leave, and in particular its code, belongs to health data. The GDPR classes it as a special category of personal data (art. 9), whose processing is subject to stricter requirements. In practice this means that access to such information should be limited to the smallest circle of people who must know it to perform their tasks.

The data minimisation principle (art. 5 section 1 letter c) and data protection by design (art. 25) lead to the same conclusion: the system should not show more than follows from the role. The split below does not replace a legal assessment in your company, but it shows how to reflect it in the settings.

How visibility is split in the working time module today

The working time module distinguishes four roles, each seeing a different scope. The employee sees themselves. HR sees the employees of its own company. The supervisor sees their sub-tree, meaning the employees assigned to their structure. The administrator sees everything.

  • The reason for an absence, that is the sick-leave code, is visible to the employee, HR and the administrator.
  • The supervisor sees only the information that the absence is justified, without the reason.
  • On their own record the supervisor cannot approve or correct anything: the role gives view-only access.
  • An employee does not see the records of other people.

Practice 1: assign roles by task, not by hierarchy

The most common mistake is giving the HR role to a person who only covers for the HR officer during leave, or the administrator role to the IT manager for convenience. The administrator sees all employee data, including sick-leave codes. The rule: the number of accounts with the administrator or HR role should be as small as possible, and every grant of a role should have a justification recorded in the documentation.

Once a quarter, review the list of people with the HR and administrator roles. People who changed position lose the role on the same day.

Practice 2: the supervisor needs a status, not a diagnosis

The supervisor must know whether an employee is absent for a justified reason, because that decides whether the record goes to the exception queue. They do not need to know the sick-leave code. The setting in which the supervisor sees only the status of a justified absence delivers this principle without additional configuration.

Make sure the same rule applies outside the system. An email to the supervisor with the sick-leave code undoes the protection built into the records.

Practice 3: document the purpose and the retention period

Every processing of data in the records should have a described purpose, legal basis and retention period in the register of processing activities. The employer keeps the working time records of an employee, which are the basis for establishing pay and other benefits (Labour Code (Kodeks pracy) art. 149 section 1), and that is the purpose of processing the hours. The purpose of processing the reason for an absence is different and has its own justification.

Retention periods are set by the company on the basis of the rules on employee documentation. The legal team should confirm them before the module is launched, not after the first inspection.

Practice 4: control access to exports and the working time card

The working time card is available as a PDF, and the hours reach HR in an export. Files leaving the system leave its permission control. Decide who downloads them, where they are saved and when they are deleted. Only the number of hours and days per employee and pay component goes to the ERP, without rates or amounts, which limits the scope of data outside the records.

Practice 5: check the settings on a test account

Before enabling the module for everyone, log in in turn as an employee, a supervisor, HR and an administrator on a test account, and check what is visible on a record with an absence. Record the result in a protocol. This is simple evidence for an audit that visibility matches the assumptions.

Checklist

Video

Frequently asked questions

Will the supervisor see that an employee is on sick leave?

They will see information that the absence is justified. They will not see the sick-leave code, which is the reason for the absence.

Can a supervisor correct their own record?

No. On their own record the supervisor role gives view-only access; the correction is approved by another person.

Does this split replace a legal analysis?

No. The system reflects the data minimisation principle, but the legal basis and retention periods are assessed by the company's legal team.

Sources

Check permissions on a test account

We will show what each role sees on a record with an absence. Book a call with the InnerWeb team.

Let's talk