Workflows overview
These pages describe end-to-end journeys that cross module boundaries. Each one has a diagram, a step table (actor, action, system response, module, notifications) and the exception paths. The module behaviour behind each step is specified in the module specs; requirements are in the PRD.
| Journey | What it covers | Modules | Main personas | Release |
|---|---|---|---|---|
| Hire to retire | New hire, pre-boarding, joining, activation, probation, job changes, separation | EMP, IAM, ORG, ATT, LVE, PAY, LMS, EXT | hr_manager, employee, line_manager | R1 (exit R2) |
| Attend to pay | Monthly cycle: attendance lock, leave, payroll run, statutory files, payslips, bank file | ATT, LVE, PAY, CLM, NTF | payroll_manager, hr_manager, finance_admin | R1 |
| Request and approval | The generic approval pattern: multi-level, delegation, escalation, on-behalf | NTF plus any requesting module | employee, line_manager, hr_manager | R1 |
| Claim to reimburse | Expense claim from capture to payout | CLM, NTF, PAY | employee, line_manager, payroll_manager | R2 |
| Field visit to travel claim | Punch, tracking, visits, daily travel, mileage claim | ATT, FFM, MOB, CLM, PAY | field_executive, sales_manager | R3 |
| Separation and F&F | Resignation or termination to full-and-final settlement | EXT, EMP, LVE, PAY, CLM, IAM | employee, line_manager, hr_manager, payroll_manager | R2 |
| Tenant lifecycle | Trial, provisioning, setup, import, parallel run, go-live, renewal, offboarding | PLT, ORG, IAM, EMP, PAY | Prospect, org_owner, platform_admin | R0 to R1 |
Conventions used in the journeys
- Events are named
<module>.<entity>.<past_tense_verb>(e.g.att.period.locked). They are published through the outbox; see the API and events catalogue. - Approvals always run through the NTF engine described in request and approval. Journey pages show only the approval outcome.
- Notifications list the default channel set: in-app (always), push for mobile users, email where the event warrants it. Tenants can change channels per event.
- Permissions are written
<module>.<resource>.<action>@SCOPE; the full grid is in the RBAC permission matrix.