HR data security software
Control who signs in and sees what
Choose sign-in methods, require 2FA for everyone, open each role down to single fields, and give every integration and AI client a narrow way in.
A security review shouldn't stall the rollout
The questionnaire arrives: sign-in, access, logging, integrations, AI, hosting. Meanwhile salary sheets are shared by link, and people who left can still sign in.
Decide how people sign in and require 2FA for all
Admins choose which sign-in methods are on: password, Google or Microsoft Entra ID. Google sign-in can be limited to your Workspace domains and Microsoft to your tenants. 2FA can be required for everyone.
Open each role to the fields and people it needs
Every role sets view or edit rights down to single fields and modules, and decides whose data it reaches: own record, reports, teams, a location or a legal entity. New custom fields stay hidden until granted.
Keep a record of who did what, including admins
Log in as is a separate, time-limited permission with restricted actions, and every session goes to the audit log. Position, pay and leave changes keep who and when, and the audit log is searchable via the API.
Give each integration and AI tool a narrow way in
The API works only through service users, each with its own role and expiring tokens. Webhooks are signed. AI clients via MCP act with one person's permissions, and the assistant changes nothing without confirmation.
Collect consent and set how long candidate data stays
Recruiting runs consent management under GDPR: candidates get a consent request with your privacy policy and can ask to edit or delete their data. Anonymous survey results stay hidden until 3 people answer.
Security settings that every module follows
Sign-in rules, roles and the audit log apply across Core HR, Recruiting, Performance and integrations, so reviewers check one access model, not one per module.
How does Skailer handle HR data security?
Skailer lets admins choose sign-in methods (password, Google or Microsoft Entra ID, limited to your domains and tenants) and require 2FA for everyone. Roles set view or edit rights per field and module and limit them to reports, teams, locations or legal entities. Log in as is a separate, time-limited permission, and each session goes to the audit log. Integrations use service users, webhooks are signed, and AI acts within user permissions. SAML and SCIM aren't supported today.
How much manual work the model takes off HR
COMPLIANCE CHECKS
OFFBOARDING
DOCUMENT APPROVAL
The questions reviewers ask, answered
| Question | Answer |
|---|---|
| How do users sign in? | Password, Google or Microsoft Entra ID |
| Can we require 2FA? | Yes, for the whole organization |
| SAML SSO or SCIM? | Not today; Google and Entra ID sign-in instead |
| Who can see salaries? | Roles with compensation access, in their scope |
| Can admins act as users? | Only with Log in as: time-limited and logged |
| Is there an audit log? | Yes, searchable through the API |
| How do integrations connect? | Service users with roles and expiring tokens |
| Are webhooks secured? | Signed, with a secret you can rotate |
| What can AI see and change? | What the user may see; changes need a confirm |
| What if someone leaves? | Duties go to a successor; sign-in is disabled |
How we work through your security review
See how teams use Skailer
Security at Skailer, answered
What does HR data security cover in Skailer?
Sign-in methods and required 2FA, role-based access down to single fields, Log in as limits and the audit log, service users and signed webhooks for integrations, AI within each user's permissions, and consent and retention for candidates.
Does Skailer support SSO?
Can we require two-factor authentication?
Can admins see everything?
Does Skailer support GDPR for candidate data?
How do integrations and AI tools reach HR data?
Send us your security questionnaire
We'll return the answers and show sign-in, roles, audit and integrations in a demo account.