Separate people views
Distinguish application membership from site-worker records.
Site workers
Keep site workers clear without creating another workforce database.
Maintain supported site-worker records separately from application users, then use the same canonical workers in daily attendance.
Two different people records
Application access and site attendance are not the same thing.
An invited staff member needs role-based access. A worker recorded on the daily roster needs an operational worker record. Mixing them confuses access and attendance.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Choose the people type
Use app users for access and site workers for the operational roster.
- 02
Maintain the worker
Add or update only supported worker details.
- 03
Use the correct site
Keep the worker available in the relevant site context.
- 04
Record attendance
Mark the canonical worker through the existing daily roster.
What worker management covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Supported worker details
Maintain the operational information exposed by the current contract.
Site context
Use worker records with supported site and attendance workflows.
Permission-aware actions
Only authorised roles can maintain the worker directory.
One workforce source
The attendance roster uses canonical site-worker records.
Current evidence shows the site-worker roster and the roles reference that governs access to supported people workflows.
- No duplicate workforce store
- Worker and app access stay distinct
- Attendance reuses canonical records
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Owner or Admin
Keep staff access and worker records understandable.
Project manager
Maintain supported site-worker information and assignment context.
Supervisor
Use the current workers in the daily roster.
Workforce boundary
Worker records are operational—not payroll, biometric identity or compliance calculation.
NIYAM keeps the supported directory and attendance connection. Sensitive workforce decisions remain subject to the business’s authorised process.
- No payroll claim
- No biometric identity claim
- No GPS surveillance claim
Questions about worker management.
Straight answers about scope, review and responsibility.
Are workers also NIYAM users?
Not necessarily. App users have workspace access; site workers are separate operational records used by supported people and attendance workflows.
Does NIYAM create a second worker database for Starter?
No. The Starter experience reuses the canonical worker records and APIs.
Can every role edit workers?
No. Worker actions continue to follow existing role and workspace permissions.