HR data security: who sees what, who did what, and does the backup really restore.
User management: activation link, password reset and locked accounts
Users are listed with their role and status: active, locked or inactive; changing between active and inactive requires an explanation. Passwords are reset and the new password is shown on screen, sent by email or delivered on mobile; a user arriving via an activation link creates a PIN and opens their account, and locked accounts are listed and unlocked.
User permissions management: role and location based access
In Role Permissions V2 (Rol Yetki V2), module, tab and action permissions are granted to roles, and a user can be given extra permissions or restrictions with an end time. In a local role, a user sees only the data of the locations, that is, the branches, they are assigned to.
Data masking in HR: hide salary information, mask IBAN and ID numbers
Field Privacy (Alan Gizliliği) sets visibility per role, table and field as Hidden, Masked, View or Edit. Pay, IBAN and Turkish ID number (TC) are hidden or masked by role.
User activity log and session log: who did what
In the Security (Güvenlik) tab, user actions (audit log) can be filtered and appear in a paginated list. Sign-in and sign-out records are listed separately with a summary.
Password policy, multi-device session control and PIN verification for sensitive actions
Password rules are visible on screen, and only the Supervisor can update them. If another session is active, PIN confirmation is required at sign-in, and a password change can be enforced when needed; before a sensitive action, the session PIN is verified again.
Automatic backup: encrypted, verified, with a second copy
The backup set is produced by a scheduler in a process separate from the API; before the backup, the records' files are counted, and if an active record's file is missing, no set is produced. Backups are verified with SHA-256 and a restore list, encrypted with a key reference, copied to a second target and pruned according to the retention policy.
Data loss prevention: daily backup restore test and recovery
Whether the backup can be restored is tested every day in a separate process; recovery provides rollback from backup and the recovery code flow. Backup runs on the server; customers have no separate backup screen.
Frequently asked questions
Can you hide salary information from managers and other users?
Yes. In Field Privacy (Alan Gizliliği), fields such as pay, IBAN and Turkish ID number (TC) are made hidden or masked for each role.
How to review the audit log in HR software?
The activity log in the Security (Güvenlik) tab shows user actions in a filterable, paginated list; session records are listed separately.
How is the password policy set?
Password rules are visible in the Security (Güvenlik) tab and can be updated only by the Supervisor role.
What happens when someone logs in from another device?
If the user has another active session, web sign-in requires PIN confirmation.
Is there PIN verification before sensitive actions?
Yes. Before a critical action, the session PIN is verified again.
How is HR data backed up?
The backup set is produced automatically by a scheduler, encrypted, copied to a second target and pruned according to the retention policy.
How do you know a backup can really be restored?
Restore is tested every day in a separate process; backups are also verified with SHA-256 and a restore list.
What if a user forgets their password?
An authorized user resets the password; the new password is shown on screen, sent by email or delivered through the mobile app.
Let's talk about Pulsar HRM and your own processes.
Start with PDKS; add the field and enterprise layers as you need them.