Employees & departments
One employee record carrying role, department, legal entity, country and work context — the fields the rest of the chain depends on.
People & HR
Employee, attendance, payroll, payslip — one chain.
People operations breaks when the employee record, the timesheet and the payroll run live in three systems that have to be reconciled by hand. In Tork they are the same chain, and each link is permission-aware.
The people operations loop
Employee → Attendance → Payroll → Payslip.
The employee record is the source. Worked time and leave attach to it. Payroll reads that period. The payslip is what the employee receives. No re-keying between steps.
Attendance & leave
Who worked, where they worked and who is away — without maintaining a parallel timesheet system that payroll then has to trust.
Employee documents
Employment documents kept outside the public web root and served through controlled, permission-checked application interfaces.
Presence, not surveillance
Attendance answers who is working. That is the job.
Attendance in Tork exists to answer an operational question and to feed the payroll period accurately. It is not a productivity-scoring product, and it does not pretend to be one.
- Feeds the payroll period so worked time, leave and overtime reach the run.
- Leave has a status, not a spreadsheet colour.
- Employee self-service for their own records and published payslips.
Access without role overload
Base role, permission packs, scope.
HR data is some of the most sensitive material a company holds. Access is built from three understandable pieces rather than a matrix nobody maintains.
- Base role — one clear starting point per user.
- Permission packs — HR, Finance, Payroll, Projects, Sales, Support.
- Scope — how far that access reaches.
- Reusable templates plus a read-only auditor role for oversight.
See it against your own org structure.
Departments, entities, countries and approval chains differ everywhere. A walkthrough against yours is more useful than a feature list.