Workflow, Roles, Self-Service, and Notifications

Workflow ownership

Onboarding uses domain-owned status actions, not Workflow Service approvals. Offboarding uses controller-owned permission checks and state changes, not a reusable workflow instance. Consequently, workflow definition ownership, service-level task assignment, delegation, escalation, SLA, and approval configuration are Not implemented for this business area.

Employee self-service

• Candidates can view and accept or decline their tokenized offer; they cannot complete the HR onboarding form.
• Employees can submit a resignation, view their exit history/status, and may request rollback when permitted.
• The exit UI fixes resignation date to the current day and prevents a second active request.
• No employee checklist, document-completion, personal-profile onboarding, asset-return, or exit-interview self-service is confirmed.

Manager and HR administration

Managers with team permissions can view and decide direct-report exits and rollback requests, but cannot decide their own exit. HR administrators can perform tenant-wide decisions and process pending access revocations. Recruitment UI visibility is associated with recruiter and HR-admin roles, while backend Recruitment authorization is coarse/transitional and final entitlement parity Requires confirmation.

Generic onboarding-task administration exists in the monolith, but no active dedicated task UI was found. HR can complete the Recruitment onboarding form and use separate Employee, Payroll, Attendance, Leave, Asset, and Document surfaces; there is no consolidated readiness dashboard.

Notifications

Trigger	Verified behavior	Maturity
Exit approval	Monolith dispatches Exit.Approved using a defined notification template	Implemented
Offer acceptance	Recruitment raises event and timeline evidence	Notification delivery Requires confirmation
Onboarding completion	Recruitment raises onboarding/joined events	Notification Service consumer support Not implemented
Exit submission/rejection/rollback/completion	No notification call found	Not implemented

The Notification Service's supported event list omits Recruitment onboarding events. Event creation must not be described as confirmed delivery.

Source References

• Controllers/HrOperationsController.cs
• Data/DatabaseSchemaInitializer.cs
• microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
• microservices/src/recruitment-service/Api/Policies.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs
• Controllers/NotificationTemplatesController.cs
• UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrOperationsPage.tsx

Revision Information

• Status: Draft
• Last reviewed: 2026-07-20
• Review cycle: Quarterly