Permissions & responsibilities

The role says what someone may do. The responsibility, where.

Everyone sees only what they may see: a shift lead plans their own people, HR sees the payroll documents, employees their own plan. Who is responsible for what follows from your structure – without lists you have to keep up to date.

Simplified drawing – not a screenshot. Terms as in the product, names made up.

Roles

Build roles from capabilities – instead of hundreds of tick boxes.

The role builder asks about capabilities: people, rota, absences, time tracking, documents, training, labour costs, sensitive personal data and more.

  • Per capability a level and a reach: own only, own units or company-wide
  • Ready-made roles as suggestions – management, manager, shift lead, employee – all of them editable
  • What a role needs to read is added automatically – never a write right or more reach
  • Sensitive personal data and labour costs are capabilities of their own – granted only to those who need them

In everyday work

Permissions that grow with your structure.

No ticking marathon when someone new joins or changes department.

  • A new shift lead starts.

    Assign the role, enter her as lead of her area – done. She sees and plans her own people, not the other areas.

  • Someone wants to know who looked at their data.

    Employeefy shows who may see the person’s data right now and who viewed or exported it.

  • The holding is to look into the subsidiaries.

    Access across companies exists exactly where a responsibility reaches. Everyone else stays within their company.

Responsibility

Whoever leads a unit is responsible for it and everything below.

Company, site, area, department, team: every unit has a manager and deputies. If it has none of its own, the manager above applies.

  • "Own units" means the ones someone leads or deputises for, with everything below
  • Team leads see and plan only their own people
  • Groups: access across companies only where a responsibility reaches there
  • People without their own login are still planned – and skipped for approvals
Simplified drawing – not a screenshot. Terms as in the product, names made up.

Deputies

When the manager is away, nothing is left lying around.

Deputies are set on the unit in a fixed order. The org chart shows manager, deputy and teams – drawn from the same data.

  • You decide: to the deputy, wait, or one level up
  • The top manager’s requests are decided one level up or by HR
  • Admins may take over the manager’s step, never HR’s
  • The help explains in plain words who decides when the manager is away

How approvals work

Employeefy org chart with leads, deputies and teams

Traceable

Who may see it – and who has seen it?

For every person Employeefy shows who currently has access to their data and who has viewed or exported it.

  • Change log for every record – append only, nothing overwritten
  • Access log: who viewed or exported a person’s data
  • "Authorised": who may currently see a person’s data
  • Two-factor sign-in, devices and sessions, rules per company

Questions

Briefly answered.

Does a team lead see other teams’ data?

No, unless their role explicitly reaches further. With the reach "own units" they see the units they lead or deputise for, and everything below.

Can we create our own roles?

Yes. The supplied roles are suggestions. In the role builder you choose level and reach per capability – or adjust individual permissions.

How do deputies work?

Every unit has a manager and deputies in a fixed order. If the manager is away, a request goes to the deputy, waits or moves one level up, according to your rule.

Does this work for several companies?

Yes. Parent company and subsidiaries sit in one installation; who accesses what follows the responsibilities – across companies too, if you set it up that way.

Show us how you plan today.

In 30 minutes we walk through your business together – and you see what your rota looks like with Employeefy.