Decide who can do what, down to the toggle
Ferio runs on software roles you define: each built from individual permission nodes. Flip exactly what a role can see and do, give it a name and a default dashboard, and assign it to your people.
How it works
in three steps
Start from a role
Use the built-ins (HR Admin, Team Lead, Employee) or create your own, with a name in English and Hungarian.
Toggle what it can do
Switch individual permission nodes on or off, grouped into Leave management and Administration. Nothing is all-or-nothing.
Assign it to people
Give each person a role. What they can see and do across the workspace follows it: nothing else to wire up.
Built-in to start, custom when you need it
Ferio ships with HR Admin, Team Lead and Employee, and you can add your own. Each role has a name (in English and Hungarian) and a default landing dashboard, and the Super Admin role is protected, so the keys can't be toggled away by accident.
Every role, built from individual nodes
A role isn't a fixed tier: it's a set of permission nodes you flip one by one. Leave management covers viewing own / team / all leave, requesting, approving, cancelling and recording for others; Administration covers managing users, teams, roles, leave types, quotas and holidays.
The hierarchy is the permissions
There's no separate org chart deciding who sees what: visibility and control come straight from a role's permissions. An employee sees their own; a team lead with the right nodes manages their team; an admin role carries the management nodes. Change a node and you change what everyone on that role can do.
Frequently asked questions
Shape access to fit how you work
Start a free trial and build a role from the ground up: toggle the nodes, name it, assign it.