Skip to main content

Recruitment Known Limitations

  • Native policy catalog is empty; explicit endpoint authorization and ownership/manager/recruiter/interviewer scopes are absent.
  • Public-token authentication, expiry, revocation, identity binding, and replay governance require confirmation; Workflow callback authentication is also unconfirmed.
  • Employee login provisioning and manager mapping are not confirmed.
  • No Recruitment Notification consumer or downstream event consumer is confirmed.
  • Offer separation of duties, thresholds, compensation governance, and document-access governance are incomplete.
  • Platform entitlement enforcement is unconfirmed; Payroll integration is absent.
  • Reporting uses current-state data; there are no dedicated formal Recruitment test projects.
  • No full parity comparator, backfill, cutover, or reconciliation tooling was found.
  • Health is process-only; no Recruitment metrics, dashboards, alerts, caching, or optimistic concurrency is confirmed.
  • Privacy, retention, consent, deletion, legal hold, and audit-access policies require confirmation.
  • Outbox retry ceiling, backoff, dead-letter, replay, poison handling, and monitoring governance are missing.
  • Dedicated policy, consent/retention, notification, outbox, reconciliation, entitlement, Payroll, requisition, and Recruitment bulk-operation UIs are absent.

These are implementation observations, not security testing findings. Remediation priority and ownership require product, architecture, security, privacy, and operations review.

Source References​

  • docs/modules/recruitment/business/limitations.md
  • docs/modules/recruitment/technical/known-limitations.md
  • docs/modules/recruitment/events/consumer-landscape.md
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • microservices/src/recruitment-service/Api/Policies.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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