Does Enclessa include HR software?

Yes, as an optional module called People. It holds employee records, an organisational structure of units and positions, effective-dated employment history, governed documents with acknowledgements, self-service change requests, and onboarding and offboarding workflows.

Does Enclessa do payroll?

No. Enclessa People holds the master data and the time records that payroll depends on, and exports them, but it does not calculate wages or make payments.

Can a manager see their team members’ salaries in Enclessa?

Not unless the organisation grants that specific field. Permissions in Enclessa People resolve per field across seven roles, so a manager can be given their people’s records without their compensation.

Can Enclessa People store records for people who do not use the platform?

Yes. An employee record exists independently of a login, so contractors, field staff and anyone else who never signs in still has a personnel file and an entry on the org chart.

Module · switch on per organisation

The personnel file, next to the work

Create your workspace See pricing

Enclessa People holds employee records — including for people who never sign in — alongside an organisational structure of units, positions, locations and cost centres. Employment, position and reporting line are stored as effective-dated periods rather than as columns that get overwritten, so the answer to "who reported to whom last March" is a lookup rather than an argument. Onboarding and offboarding are workflows that actually reach into accounts, teams, boards and time tracking instead of producing a checklist somebody has to execute by hand.

At a glance

Availability: Module, off by default
Records: Employees with or without a login
Structure: Units, positions, locations, cost centres, vacancies
History: Effective-dated, append-only
Documents: Versioned, acknowledged, audited on download
Access: Field-level permissions across seven roles

Why store history as periods instead of fields?

Because a personnel record is a timeline, and a system that overwrites the current position loses the ability to answer anything about last year. Employment, position and manager are append-only effective-dated periods, so the org chart can be rendered as it stood on any date, and a correction is a new period rather than a silent edit.

Employment, position and manager as effective-dated periods
A vacancy-aware org chart showing unfilled positions
Corrections add a period; nothing is overwritten

Who can see what?

Field-level permissions across seven roles, resolved per field rather than per screen. A manager sees their people without seeing their pay. An administrator sees structure without automatically seeing documents. Every download of a document is written to the audit log with who took it and when.

Field-level resolution, not per-page visibility
A manager sees their people, not their compensation
Audited document download
Self-service change requests that route for approval

What do onboarding and offboarding do?

They act. An onboarding workflow creates the account, adds the person to the right teams and channels, gives them the boards they need and switches on their time tracking; offboarding reverses it in the correct order and hands over what needs handing over. The workflow is the thing that happens, not a document describing what somebody should remember to do.

Account, team, channel, board and time-tracking provisioning
Offboarding that revokes in order and hands work over
Document categories with versions and required acknowledgements

How does it handle data protection duties?

Retention rules and legal holds are first-class: a hold refuses an erasure by naming itself, so nobody deletes something they were required to keep and nobody keeps something they were required to delete without knowing why. Data-subject exports are a supported operation rather than a database query somebody writes under pressure.

Retention rules and legal holds that state their own reason
Data-subject export as a supported operation
Reports and exports for the people who need numbers

What this does not do

People is off until an operator enables the module for the organisation.
There is no payroll. Enclessa holds the records payroll needs and does not calculate or pay anybody.
There is no recruiting or applicant tracking, no performance review cycle and no learning management. None of these are in scope.

Time trackingClock in and out, project time, timesheets with approval, absence with an entitlement ledger and an overtime balance.Read more MessagingTeams, channels, threads and direct messages, with search, files and a permission model checked in the data layer.Read more Task boardsKanban boards that inherit the team’s roles and link back to the conversation the work came out of.Read more

Questions

People: common questions

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.