Role-based access control for HR
Access that follows your org chart
Roles take their members and scope from org data. Managers see their reports, country HR its own country, and scopes recalculate after a reorg.
Permissions that update when people move
Access lists drift the week after a reorg
Two departments merge, a team lead moves to Berlin, and HR checks a spreadsheet of who sees what. Meanwhile Cyprus HR can still open German salaries.
Assign roles by rules on org data, not by hand
Build rules on employee attributes, and everyone who matches gets the role, including people hired next month. Combine rules as all, any, or groups of rules, so one role covers several employee groups.
Scope each role by reporting line, location, or entity
A second set of rules decides whose data a role opens: all reports at every level, teams led, departments managed, or one location or legal entity. After a transfer or a reorg, scopes recalculate on their own.
Set view or edit per field so each role gets the minimum
A manager may need a report’s time off but not their salary. Each field gets no access, view, or edit, and you can set a whole section at once. Module access is a separate layer of permission management, from leave approvals to reports.
Show each person only the employee data their job needs
The GDPR asks companies to limit who can see personal data. In Skailer, each role opens only the people and fields it needs, and new custom fields and tables stay hidden until you grant access. All HR data is stored in the EU, in the AWS Frankfurt region.
Hold a new hire's portal until onboarding is done
Before the start date, a new hire sees only a preboarding page. After it, the portal stays limited until restricting onboarding flows finish. Integrations connect as service users with their own roles.
One role model for every module and integration
Custom fields and tables define what you store, and roles decide who sees it. Records, approvals, flows, reports, SK.AI, and API integrations all follow the same roles.
How do roles and permissions work in Skailer HR?
Roles & permissions is role-based access control software for HR in the Skailer platform. Each role has two sets of rules: who receives it, by location, legal entity, job profile, or manager status, and whose data it opens, from the holder’s own profile to all reports or one legal entity. Within that scope, a role gets no access, view, or edit per field and table column, plus access to modules. Fields a role can’t edit can still change through a request with approval. All HR data is stored in the EU, roles are included in the price with no add-ons, and sign-in methods are set separately in security settings.
SkailerCheck what each person sees and what changed
An auditor can read every access decision without the right to edit roles. Audit reports in settings show who gained or lost each role, when, who made the change and why, and every edit to a role. They list what each role allows and who holds a given permission, and for any employee, who can see their data and whose data they see. Each report exports to a file. Log in as shows the portal as an employee sees it, and every session is logged.
HRIS access control without a security project
HRIS tools with fixed access levels are quick to set up but hard to bend. Enterprise HCM suites model almost anything through security groups and policy layers.
| Capability | HRIS, fixed access levels | Enterprise HCM security | Skailer |
|---|---|---|---|
| Who gets a role | Fixed levels such as admin, manager, and employee | Security groups by role or org | Rules and rule groups on org data |
| Scope from the org | Reporting line | Configurable by organization | All reports, teams led, departments |
| Location or entity | Varies by vendor | Usually supported | Yes, for any role |
| Custom roles | Varies by vendor and plan | Usually included | Included, with no add-on |
| Custom table access | Show or hide a field | Configurable | Per column, with separate history |
| New-hire portal access | Usually not tied to onboarding | Varies by vendor | Held until onboarding flows finish |
| Approvals | Set per request type | Configured in business processes | Routed to a manager or role, with backup approvers |
| Data location | Varies by vendor | Varies by vendor | EU, in the AWS Frankfurt region |
| Price | Often sold in modules or add-ons | Custom enterprise pricing | From €12 per employee per month, all modules included |
How roles and permissions work in Skailer
See how teams use Skailer
Roles & permissions: common questions
It's Roles & permissions, the access model of the Skailer HR platform. HR decides who receives each role and whose data it opens, then sets view or edit per field, table column, and module. Built-in roles cover the basics, and custom roles are included in the price.
Yes. Assign a role to HR team members in one location and limit its scope to the same location or legal entity. Profiles from other offices stay out of scope.
Yes. A role's scope can include all reports across every level. You can also limit it to teams the person leads or departments they manage or belong to.
New custom fields and tables stay hidden until a role gets access. Each field gets no access, view, or edit. In a table, read-only roles see the columns you choose, and Full edit access covers the whole table.
Skailer combines the roles and takes the highest permission that applies. If one role lets a person view a field and another lets them edit it, they can edit it.
No. Flows run onboarding; Portal access decides what a new hire sees while it runs. The portal stays limited until the start date and until every restricting flow has finished.
Roles & permissions is included in the Skailer price, which starts at €12 per employee per month. Skailer doesn’t sell add-ons, so custom roles, field-level permissions, and every other module come with it.
The GDPR principle of data minimisation says people should see only the personal data they need. In Skailer, each role opens only the people and fields its job needs, and new fields stay hidden until you grant access. Skailer stores HR data in the EU, in the AWS Frankfurt region, and a Data Processing Agreement (DPA) is available to every customer. Your company still decides who needs which data.
Roles decide what people can change on their own. If a role can’t edit a field, such as bank details, the employee sends a change request, and an approver reviews it. Approval steps in leave policies and flows go to the employee’s manager or to a role, so requests reach the new approver after a transfer. When an approver is away, a backup reviews the request.
No. Skailer assigns roles by rules on HR data, such as location, legal entity, or manager status, so roles update when the employee record changes. Sign-in is set up separately: password, Google, Microsoft Entra ID, or your own OpenID Connect provider. SAML and SCIM aren’t supported today.
Open the audit reports in settings: pick an employee to see who can view or edit their data, or pick a permission to see who holds it. Use Log in as to see the portal the way a specific employee sees it; every session is logged.