Team · People Workspace
Give every people workflow one dependable employee record.
Payroll, scheduling and access drift when each team keeps its own version of who works where.
This is a capability inside Lightning Pharos, not a separate product.
Create or update an employee's current business record.
01 · What ships
The complete working surface.
The org: who works here, in which team, under whom.
- 01
Employee records with business job role, business unit, department, team, manager, and location
- 02
Employment status, joining, and termination details
- 03
A login bridge from the employee to their workspace identity
- 04
Competency and readiness data used by workforce workflows
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
Create or update an employee's current business record.
- 02 / 03
Governed event
Business role, team, manager and location stay on the employee record.
- 03 / 03
Connected result
People workflows use the current employee details. This is not an effective-dated organisation history or a security-role editor.
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.
There is no position or grade model and no dedicated dated history for organisation assignments. Business job roles are not security roles.
Bring your exact workflow to a walkthrough and we will show where Pharos fits and where it does not.
Continue the system