KVKK-oriented process design: masking sensitive data and logging access
How do you set up KVKK-oriented process design? Using the personnel file, we explain role-based scope, masking of sensitive fields and access logging.
Protecting personal data usually begins with a policy document, but in reality it is tested on a screen: who sees an employee’s national ID number, on which page and how often? KVKK-oriented process design is a design approach, KVKK being Turkey’s personal data protection law, that limits access by role in business processes carrying personal data, hides sensitive fields and records the access that takes place.
This article is not a legal assessment; it shows how software can help set up a process. As the example we use the personnel file, one of the areas with the highest density of personal data, and the Digital Personnel File & HR Management module of YazSis KurumsalPortal.
Why is the personnel file a good example?
A personnel file gathers documents such as identity details, bank account, medical report, diploma and contract in one place. If the file sits in a folder or on a shared drive, both limiting access and knowing who has looked become difficult. Someone can look at another person’s file with their own permission, a document can go to the wrong person by e-mail, and a former employee’s folder can stay open for years. That is why security design makes a concrete difference here.
Five design principles
The principles below complement each other. None of them alone is enough to say “the problem is solved,” but when applied together, the control over personal data can be shown both in day-to-day work and at a moment when you are being questioned.
1. Limit access by role. Letting everyone see everything is easy but indefensible. In the module, HR, authorized managers and employees see only the scope defined for their roles; which role sees what is set according to the organization’s processes. Role-based data scope is the foundation of this approach; when permission is tied to the duty rather than the person, it also becomes easier to rethink access the moment the duty changes.
2. Mask sensitive fields. To do their job, a person may not need to see the whole national ID number or IBAN. These fields are masked in the portal. When fields are masked, someone looking at the screen or seeing a screenshot cannot reach the full information. This also reduces the risks that can arise when a screenshot is shared or someone looks over a shoulder.
3. Log access. Limiting access is not enough; the access that takes place must leave a trace. Accesses to documents are kept in a document access log, and the platform also has an audit log. When a question comes up, “who opened this document, and when?” can be answered. The same approach appears in the visitor KVKK consent record and the anonymous survey option: when data is collected, consent and privacy have been thought through from the start.
4. Track missing and expiring documents. An out-of-date file is a risk too. Which documents are mandatory is defined with a dynamic document matrix and assigned to each employee; what is missing is tracked on a completeness dashboard. Document versions and approvals are stored, and a warning is given for documents that have expired or are about to. That way the file is not an archive graveyard but a record that is kept current.
5. Keep data where you can control it. KurumsalPortal runs on the customer’s own server, and data is not sent to a third-party cloud. Personnel cards and personnel file documents also sit on the organization’s own server; access is limited by role-based permission. When the answer to the question of where the data is is clear, describing the process and preparing for an audit both become easier.
Three common mistakes in design
- Granting permission by person: Permissions given one by one because “Mr. Ahmet should be able to look too” turn over time into a permission list nobody remembers. A scope defined through role and duty is both simpler and easier to audit.
- Thinking about masking only on the screen: If the same information appears in full in an exported report or in a file sent by e-mail, the mask on the screen alone is not enough. How much data will be shown in which output has to be decided from the start.
- Keeping a log and never looking at it: An access log creates value not only when an incident happens but also when it is reviewed at regular intervals. An unusual access is noticed only when someone looks at the log.
Five questions for your own process
- Who can open an employee’s personnel file right now; is this list made up of people who really need it?
- Are full national ID numbers and IBANs shown on screens and in reports?
- Can you show, looking back, who accessed a document?
- How do you notice missing or expired documents today?
- When an employee leaves or changes duties, who closes their access, and when?
Protecting data begins with knowing who sees it.
You can look at all the details of the module on the Digital Personnel File & HR Management page, and at the other modules that share the same controls on the KurumsalPortal page.
Frequently asked questions
What does KVKK-oriented process design mean?
It is a design approach that limits access by role in business processes carrying personal data, hides sensitive fields and records the access that takes place. YazSis KurumsalPortal offers these controls to help you set up a KVKK-oriented process.
How are sensitive fields protected in the personnel file?
Sensitive fields such as the national ID number and IBAN are masked. Access is limited by role-based permission; accesses to documents are kept in the document access log.
How are missing personnel file documents tracked?
The document matrix assigned to each employee is compared with the documents collected, and what is missing is tracked on the completeness dashboard. A warning is given for documents that have expired or are about to.
Where is personnel file data stored?
KurumsalPortal runs on the customer’s own server; personnel cards and personnel file documents are also kept on the organization’s own server.
More articles
How to manage date holds at a wedding venue: viewing, time limit and confirmation
A date hold lets a couple reserve a day provisionally until they decide. When the end of the hold, the viewing time and the next couple in line appear in one calendar, date mix-ups become rarer.
November 17, 2026 · 5 min readWhat is a ticketing system? How to set one up and get support requests out of e-mail
A ticketing system turns every support request into a numbered record with a clear owner and status. How it differs from an e-mail thread, the ticket lifecycle, the decisions to make before setup and its use in IT support.
November 17, 2026 · 8 min readField service tracking: Excel or software? When to switch and what to look for
Excel works for service records with few devices and few technicians. We compare what happens when equipment history, parts, SLAs, signatures and invoicing come together, and when to move to service tracking software.
November 17, 2026 · 8 min read