A new HR specialist receives a login to the payroll system, a key to the personnel files cabinet and access to the recruitment mailbox in her first week. Nobody asks about an authorisation, because “she signed the GDPR clause with her contract”. Six months later an auditor asks for a list of people with access to employee data, with the date and scope of each person’s access, and the company rebuilds it from managers’ memories and account histories.
GDPR staff authorisation is one of those concepts still surrounded by habits from before the GDPR. Some of them are rooted in the law, some are only practice, and the difference decides how many documents a company really has to keep. The English text of the GDPR speaks of persons “acting under the authority of the controller”, while the Polish text uses the word “upoważnienie”, and a written authorisation with a register of authorised persons is a Polish practice that other Member States may not follow. For the team responsible for cybersecurity, authorisation also has a technical side: every account in a system holding personal data should correspond to a decision of the controller.
What is a GDPR staff authorisation to process personal data?
A GDPR staff authorisation to process personal data is a decision of the controller or processor that admits a specific person to the data and sets the instructions under which they may process it. Article 29 GDPR is entitled “Processing under the authority of the controller or processor” and provides that any person acting under that authority who has access to personal data shall not process those data except on instructions from the controller, unless required to do so by Union or Member State law.
Authorisation also matters for definitions. Article 4(10) GDPR excludes from the “third party” persons who, under the direct authority of the controller or processor, are authorised to process personal data. An HR employee who opens a personnel file as part of their duties is therefore not an external recipient but part of the controller’s organisation.
Legal position as of 18 October 2026. Articles 4, 29, 30 and 32 GDPR have not been changed by any amending act since the regulation was adopted in 2016.
Where does the GDPR obligation to authorise staff come from?
The obligation comes from two provisions: Article 29 sets out the principle, and Article 32(4) requires the controller and processor to act. Article 32(4) requires them to take steps to ensure that any natural person acting under their authority who has access to personal data does not process them except on instructions from the controller.
Placing this requirement in the article on security of processing matters. Authorisation is not an HR formality but an organisational measure that limits the circle of people with access to data and binds them to the controller’s instructions.
Neither provision gives a template, a form or a list of elements of an authorisation. The framework comes from the accountability principle in Article 5(2): the controller must be able to demonstrate compliance with the processing principles. The UODO guide for employers (in Polish) of 4 October 2018 applies it directly to authorisations: in line with accountability, the controller should be able to prove that it granted the authorisation to process data.
Who grants the authorisation and to whom?
The controller authorises its people and the processor authorises its own, because Article 29 and Article 32(4) refer to persons acting under the authority of the controller or processor. The decision can be taken by a person representing the controller or by a manager to whom this power has been delegated in internal rules.
The group of people is wider than the list of permanent employees. According to the UODO guide, an employee in an employment relationship processes data on the basis of the authorisation granted. The same applies to contractors and self-employed persons if they use the controller’s resources, such as systems and premises, and act on its instructions.
The guide also settles two cases that raise doubts in practice. A temporary worker is authorised by the user employer, provided that the worker has access to data as part of their duties, and an occupational health and safety officer or a trainer who is a natural person should hold an authorisation for the data of training participants.
How does authorisation differ from a data processing agreement?
Authorisation concerns people acting within the controller’s organisation, whereas a data processing agreement under Article 28 GDPR concerns an external entity processing data on the controller’s behalf. The dividing line is whose resources are used and within whose organisation the processing takes place.
UODO gives examples of entities that process data in their own systems and hand over the result to the controller: an accounting firm, a hosting company, and recruitment or training carried out outside the employer’s structure. Such entities are not the controller’s staff, so a data processing agreement is needed, not an authorisation.
Both instruments share the confidentiality requirement. Article 28(3)(b) GDPR requires the agreement to oblige the processor to ensure that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. The supplier’s employees therefore also act under authorisations, only they are granted by their own employer.
Key points:
- Authorisation admits a person to data within the controller’s or processor’s organisation (Article 29 and Article 32(4) GDPR).
- According to UODO, a contractor working in the controller’s systems and on its instructions acts under an authorisation.
- An external company processing data in its own systems needs a data processing agreement under Article 28.
Does the authorisation have to be in writing?
The GDPR does not specify the form of authorisation, but Polish employment law requires it in one important case. Article 22¹b § 3 of the Polish Labour Code (in Polish) provides that only persons holding a written authorisation issued by the employer may be admitted to process employees’ special category data under Article 9(1) GDPR referred to in § 1 of that provision.
The same provision obliges the persons admitted to such data to keep them confidential. An HR department that accepts a health certificate handed over on the employee’s own initiative should therefore have people with a written authorisation, not just an account in the system.
Outside such specific provisions, the form follows from accountability. An oral authorisation is hard to demonstrate, so a practical choice is a document signed by the authorised person or a system record showing who granted access, to whom, when and to what extent.
What should an authorisation to process personal data contain?
An authorisation should identify the person, the scope of data or processing activities, the period of validity and the instructions under which the person is to process the data. Since Article 29 binds the authorised person to the controller’s instructions, an authorisation without a defined scope does not say what those instructions are.
A practical template covers the name and position, the categories of data or processing activities from the record, the systems and paper files the person has access to, the date of granting and expiry, the person granting it, and confirmation that the person has read the confidentiality obligation and the security rules. The scope is easiest to describe by referring to activities in the record of processing activities, for example “calculating and paying salaries”, instead of writing “personal data to the extent necessary”.
An authorisation that is too broad is as bad as none. The wording “for all data processed in the company” does not limit access, so it does not fulfil the function that Article 32(4) assigns to authorisation as a security measure.
Does the GDPR require a register of authorised persons, and how do you keep one?
The GDPR does not mention a register of authorised persons: it is not in Article 29, in Article 32(4) or among the entries of the record of processing activities under Article 30(1)(a)–(g). The Polish custom of keeping such a list has a different source.
The obligation came from the Polish Personal Data Protection Act of 29 August 1997 (in Polish). Article 37 admitted to processing only persons authorised by the controller, and Article 39(1) required a register of authorised persons with the name, the date of granting and expiry and the scope of the authorisation, and, for processing in an IT system, also the user identifier. For processing by businesses, the Act ceased to have effect on 25 May 2018 under Article 175 of the new Personal Data Protection Act of 10 May 2018 (in Polish); some provisions, including the chapter on data security, remained in force temporarily only for processing to combat crime.
The practice of keeping a register therefore derives from the repealed Act, not from the GDPR. That does not make it redundant: since the controller should be able to prove that it granted an authorisation, a register is the simplest way to do so for everyone at once rather than document by document.
A register works as evidence when it matches the accounts in your systems and is updated with every staffing change. A spreadsheet updated once a year shows intentions, not the actual state.
A good starting point is the fields of the former Article 39(1): the person, the date of granting and expiry, the scope and the identifier in the system. The last field matters most for the IT team, because it links the controller’s decision to an account that can be checked in the logs. It is worth adding the person who granted the authorisation and a reference to the document or to the request in the ticketing system.
The register does not have to be a separate document. If your identity management system stores access requests with approval, date and scope, it can serve this purpose, provided it also covers paper files and systems outside the domain directory.
How does authorisation connect with access control in IT systems?
Authorisation is an organisational decision and permissions in systems are its technical implementation, so both records should match. Article 32(1)(b) GDPR requires the ability to ensure the ongoing confidentiality of processing systems and services, and a mismatch between authorisations and accounts undermines that confidentiality.
A mismatch can take two forms. The first is an account without an authorisation, for example a supplier’s technical service account or an intern’s account created “for a moment”. The second is an authorisation without technical control, when the document limits the scope to HR while the system role also shows the payroll of the whole company.
The principle of least privilege, familiar from cybersecurity, translates Article 29 into the language of a systems administrator: a person has access to what their instructions require and nothing more. A periodic access review, in which a manager confirms the list of people with access to their department’s data, brings both worlds together in a single document.
When do you need to change or withdraw an authorisation?
You change an authorisation with every change of duties and withdraw it when the working relationship ends, ideally on the same day the account is disabled. Article 24(1) GDPR requires technical and organisational measures to be reviewed and updated where necessary, and authorisation is one of those measures.
Internal moves are easy to overlook. An employee who moved from HR to sales keeps the old permissions if the job change process does not include an access review. From a data protection point of view, that person then has access without the instructions Article 29 requires.
It is worth recording the withdrawal of an authorisation with a date rather than simply deleting the entry. A register that shows the period of authorisation allows you to establish after an incident whether the person had the right to the data at the moment they accessed it.
How do you build an authorisation process step by step?
You build the process around staffing events, because they change the group of people with access to data. Each event has its own decision, a responsible person and the trace left in the documentation.
| Event | Authorisation decision | Who is responsible | Trace in the register | Change in systems |
|---|---|---|---|---|
| Employment or civil-law contract | scope according to activities in the record | line manager and the person representing the controller | date granted, scope, identifier | accounts created with roles matching the scope |
| Arrival of a temporary worker | does the worker have access to company data | user employer | as for employment | temporary account with an expiry date |
| Access to employee data under Article 22¹b of the Labour Code | written authorisation | employer | written document in the files | role with access only to that data |
| Change of position | new scope, withdrawal of the old one | previous and new line manager | date both scopes changed | review and removal of unnecessary roles |
| Periodic review | confirmation or correction of the list | head of department, with the DPO | dated review record | removal of accounts without authorisation |
| End of the working relationship | withdrawal of the authorisation | line manager and HR | date of expiry | accounts blocked on the day of departure |
If the process ends with a signature on a document rather than with the change in systems from the last column, authorisations and permissions drift apart after the first change of position.
How can nFlo help you put authorisations in order?
nFlo helps put authorisations in order as part of the Data Protection Officer (DPO) Outsourcing service in the “Governance, risk and compliance” area. The service covers performing the DPO function, oversight of GDPR compliance, an initial GDPR audit when taking over the function, employee training and contact with UODO.
Article 39(1)(b) GDPR lists among the DPO’s tasks monitoring compliance with data protection policies, including the assignment of responsibilities, staff training and related audits, so reviewing authorisations and registers falls within that role. nFlo does not provide legal advice. If you want to put authorisations in order in your organisation, contact us. Wider background on the controller’s obligations can be found in our GDPR guide and in the GDPR glossary entry.
What else should you know about staff authorisations to process data?
Does the GDPR require a written authorisation to process personal data?
Not directly. Article 29 and Article 32(4) GDPR do not specify the form, and written form is required by specific provisions, for example Article 22¹b § 3 of the Polish Labour Code for employees’ special category data.
Do you have to keep a register of authorised persons?
The GDPR does not mention it. The obligation came from Article 39(1) of the Polish Act of 1997, which ceased to apply to businesses on 25 May 2018, and today a register helps demonstrate that authorisations were granted, in line with accountability.
Does a contractor need an authorisation or a data processing agreement?
According to UODO, an authorisation, if they work in the controller’s systems and premises and on its instructions. A data processing agreement applies to entities processing data in their own systems.
Who authorises a temporary worker?
The user employer, provided that the temporary worker has access, as part of their duties, to data controlled by that company.
Is an authorised person a third party under the GDPR?
No. Article 4(10) GDPR excludes from the definition of a third party persons who, under the direct authority of the controller or processor, are authorised to process data.
