Recruitment Document Reference Catalog

Document	Recruitment responsibility	Document Service responsibility	UI/access evidence	Governance gap
Resume	Candidate/application metadata and native reference	Stored content in native design	Public/HR upload and protected view/download	Consent, retention, delete, per-document authorization
Candidate document	Candidate document reference	Stored content	Native upload/list/download API; no comprehensive standalone UI	Delete, lifecycle sync, reconciliation
Offer letter	Offer/letter reference and hiring state	Stored/generated content where integrated	Offer generation/download action	Template approval, retention, access, orphan cleanup

No document content or sample data is included. Privacy, retention, deletion, legal hold, consent, malware scanning, and audit-access ownership require confirmation.

Source References

• microservices/src/recruitment-service/Domain/Recruitment/Candidate.cs
• microservices/src/recruitment-service/Domain/Recruitment/Offer.cs
• microservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentCandidatesPage.tsx
• UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOffersPage.tsx

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.

Related Articles

• Recruitment module
• Recruitment technical documentation

See Also

• Recruitment API
• Recruitment known limitations

Keywords

• Recruitment
• Hiring lifecycle
• Draft documentation

Revision Information

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