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.

Role-based access control HR software in Skailer: role editor with assignment and scope rules
01Scopes from your org chart
All reports, teams led, or departments managed. No lists.
02Offices stay separate
Scope any role by location or legal entity, for any HR team.
03Custom data, column by column
New fields stay hidden until a role gets access to them.
04Portal opens after onboarding
A new hire sees a preboarding page until onboarding ends.
The problem

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.

Who gets a role

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.

01Roles from org data
assign by location, department, legal entity, or job profile
02Rule groups
match all rules, any rule, or a combination of rule groups
03Position-based roles
manager, department head, and team lead status as conditions
04Custom field values
target a cost center, an office, or any other value you store
HRIS user roles assigned by rules on location, department and job profile in Skailer
Whose data

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.

01All reports, every level
managers reach their whole reporting tree, down to the last level
02Teams and departments
teams the holder leads, departments they manage or belong to
03Location and legal entity
separate country HR teams inside one Skailer account
04Departed managers drop out
rules skip anyone whose termination date has passed
HR data access permissions scoped by location and legal entity in Skailer
Field & module permissions

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 a whole section can be set at once. Module access is a separate layer, from leave approvals to reports.

01Field-level rights
view or edit per field group, custom field, and table column
02Compensation in layers
compensation lines and total cost of employment as separate rights
03Custom roles on every plan
add roles beyond the built-in ones without changing your plan
04Module and settings access
open recruiting or reports without opening people data
HR software permissions with view or edit per field group in Skailer
Custom data access

Grant access to custom data so nothing shows by accident

Work permits, certifications, issued equipment: data no standard HR tool planned for. A new custom field or table stays hidden until a role gets access, and read-only roles see only the columns you open.

01Hidden by default
new custom fields and tables stay hidden until a role gets access
02Column-level viewing
read-only roles see only the table columns you pick
03Full edit access
one switch lets HR ops add, edit, and delete records in a table
04History on its own switch
decide separately who sees past records and change authors
New hires & integrations

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.

01Limited until start date
before day one, new hires see only their preboarding page
02Held by restricting flows
you pick which onboarding flows keep the portal limited
03Manual release with reason
who lifted the limit, when, and why stays on record
04Service user roles
each integration gets only its role's access and no employee seat
Full-cycle HR

One role model for every module and integration

Custom fields and tables define what you store; roles decide who sees it. Records, 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 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 module access. Sign-in methods are set separately in security settings.

Audit & control

Check what each person sees and what changed

Creating, changing, and deleting a role goes to an audit log that authorized roles can search. Log in as shows the portal as an employee sees it, and every session is logged.

HRIS access control: log in as an employee to check what they see in Skailer
Skailer vs. the alternatives

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.

CapabilityHRIS, fixed access levelsEnterprise HCM securitySkailer
Who gets a roleManual lists or basic conditionsSecurity groups by role or orgRules and rule groups on org data
Scope from the orgReporting lineConfigurable by organizationAll reports, teams led, departments
Location or entityVaries by vendorUsually supportedYes, for any role
Custom rolesOften on higher plans onlyUsually includedOn every plan
Custom table accessShow or hide a fieldConfigurablePer column, with separate history
New-hire portal accessUsually not tied to onboardingVaries by vendorHeld until onboarding flows finish
How it works

How roles and permissions work in Skailer

01Start from the built-in roles
Set what employees see in Myself and All employees, then adjust what Managers and Team leads see and edit.
02Create a custom role
Name the role and decide who gets it with rules on location, department, job profile, or any custom field.
03Set permissions and scope
Choose access per field and table column, open the modules the role needs, and define whose data it reaches.
04Save and check
Changes apply on save. Use Log in as to see the portal the way a role member sees it, with the session logged.
Customer stories

See how teams use Skailer

Food techDodo Brands: technical experts join interviews without seeing salary data
Read the story
PaytechA paytech company restores cross-team visibility in under an hour
Read the story
Classifieds · 5 countriesLarixon builds its first HR system across five countries
Read the story

Roles & permissions: common questions

What is role-based access control for HR in Skailer?

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 available on every plan.

Can I restrict HR access by country or legal entity in Skailer?

Can managers in Skailer see their indirect reports?

How does Skailer control access to custom fields and tables?

What happens if an employee has more than one role?

Does Roles & permissions run onboarding?

See roles built around your structure

Book a demo, and we'll map your locations, managers, and custom data to Skailer roles.

We'll set up one custom role during the demo.