It starts with name and date of birth; registry number, Social Security (SGK), civil registry (NVI) fields, contract, cost center, ISCO-08 and ~50 optional fields all live on the same record. Documents, organization, family, asset assignments and the self-service portal are all tied to a single person — built into Turkish labour law.
The employee and their personnel detail are created in a single atomic operation. The only required fields are first name, last name and date of birth; the remaining ~50 fields can be filled in from the detail page whenever you like.
For a fast hire you enter only first name, last name and date of birth; the person enters the system and the personnel details are completed later. Identity and financial fields can stay empty, but when entered they are validated for regulatory compliance — you never proceed with incorrect data.
Two people looking at the same employee profile don't see the same data. Sensitive fields are masked at the record level according to the user's permissions — they are never sent to an unauthorized user at all.
Salary, IBAN, national ID and SGK number are hidden by role; for a user without permission these fields return null.
Masking works on both the employee list and the single employee detail; allowed fields are determined by the user's permissions.
A manager who isn't on the HR team is prevented from seeing a subordinate's salary or IBAN; data minimization is the default behavior.
Every document is attached to the employee record, stored by type, and each access is written to the audit trail. Special-category documents are stamped automatically.
Driver's licence, residence permit and passport dates are gathered in a single panel; an expired residence permit for a foreign worker is an administrative-fine risk.
Driver's licence, residence permit and passport validity are read from the personnel detail, and those due to expire or already expired are listed.
Days remaining are calculated against an adjustable warningDays threshold (1–180 days), and each document falls into a status.
The list is sorted by days remaining and a summary counter is returned; export to CSV for renewal planning.
Department tree, position fill rates and an org chart; master data is normalized automatically, and an empty tenant starts with common positions.
Seven sub-records that extend the employee profile; all are attached to the personnel detail and tenant ownership is verified on every operation — you cannot reach another tenant's record.
Type (RESIDENCE / CONTACT / BIRTH), country, province, district, neighborhood, full address, postal code.
Spouse, child, parent, sibling; national ID, date of birth, gender, dependency status.
Level, school, department, graduation and GPA; certificate/diploma URL.
Name, issuing body, expiry date, document URL; those that have expired are listed separately.
Language, level (A1, A2, B1, B2, C1, C2, NATIVE), whether certified, certificate name.
Type (LAPTOP / PHONE / CAR / KEY / CARD), name, serial no, assignment and return date.
Name, relationship (mother/father/spouse/sibling…), phone, email, address, primary flag.
A classic HR practice for employee engagement: upcoming birthdays and work anniversaries in a single panel — a list for a congratulatory message or a small celebration.
Employment and income certificates are generated as PDFs and pass through a state machine; online national-ID verification and KEP configuration establish the official integration layer.
The employment certificate and income certificate are generated as PDFs and uploaded to Azure Blob; the income certificate is fed from the last 3 payroll line items.
First the offline Mod-11 algorithm, then a SOAP request to the NVI KPS Public service (national ID + first name + last name + year of birth).
The KEP (registered electronic mail) provider, sender address, username and password are kept in tenant settings; the connection test sends a TLS ping to the provider's server.
Real KEP send/receive integration is currently on the roadmap — today the configuration record and the TLS connection test to the server work fully, while the actual sending of a KEP message (PTT/TNB API) is the next step. Online NVI verification requires a KPS Real subscription agreement; when the service is closed to anonymous access, the system reports this clearly. The offline Mod-11 algorithm check always works.
The employee logs in with a magic link sent to their email; they view their own payslips, leave, advances and documents, and update their personal information within a restricted whitelist.
In the demo, let's open an employee profile from your own team — see identity verification, documents, the organization and the self-service portal with your own eyes.