HR · People Workspace
Keep employee documents verifiable before they lapse.
An employee document loses trust when the file, checksum, version and expiry are stored separately.
This is a capability inside Lightning Pharos, not a separate product.
Upload or replace an employee document.
01 · What ships
The complete working surface.
Employee documents with bytes, versions, checksums, and expiry evidence.
- 01
Real file bytes stored against the employee document record
- 02
Checksums and downloads for document evidence
- 03
Expiry dates, versions, and uploader history
- 04
Archive and restore without erasing the record
02 · Connected work
One action. One history. More than one team.
Pharos keeps the source action and the records it affects on one inspectable event path.
- 01 / 03
Source action
Upload or replace an employee document.
- 02 / 03
Governed event
The bytes, checksum, uploader, version and expiry stay on the record.
- 03 / 03
Connected result
HR can download, archive or restore the evidence without erasing its history.
03 · What it needs
Ready inside every Pharos workspace.
No additional module is required before this capability can be switched on.
04 · Where it stops
The boundary is part of the product.
This is not a full HRIS. Employee master data belongs to Team; broad profile self-service, onboarding, e-signature, absence, and case management are not included here.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system