Recruitment Business Integrations
Summary
Recruitment has confirmed boundaries with Employee, Workflow, Document, Gateway, Identity, Platform, and messaging; Payroll and Notification behavior is incomplete.
Audience
Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.
Overview
Recruitment has confirmed boundaries with Employee, Workflow, Document, Gateway, Identity, Platform, and messaging; Payroll and Notification behavior is incomplete.
Integration landscape
| Boundary | Confirmed behavior | Maturity |
|---|---|---|
| Employee | Synchronous provisioning on onboarding completion | Partial; login and manager mapping gaps |
| Workflow | Requisition approval only | Transitional |
| Document | Resume/candidate-document storage and offer-letter generation | Transitional dependency |
| Gateway | Feature-controlled native/compatibility ownership | Transitional |
| Identity | Portal authentication and service JWT middleware | Foundation authorization |
| Platform | Module, offer-letter feature, and opening-limit catalog entries | Foundation; enforcement not confirmed |
| Notification | Recruitment emits events; no consumer confirmed | Not implemented |
| Payroll | No Recruitment interaction found | Not implemented |
Platform catalog entries do not prove that opening limits or offer-letter entitlements are enforced by Recruitment.
Requires confirmation
Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.
Source References
microservices/src/recruitment-service/Program.csmicroservices/src/recruitment-service/Application/Commands/OnboardingCommands.csmicroservices/src/gateway-api/Program.csmicroservices/src/platform-service/Data/FeatureManagementSeeder.cs
Related Articles
See Also
Keywords
- Recruitment
- Hiring lifecycle
- Integrations
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly