Skip to main content

Recruitment Public Token Operations

Purpose​

Defines safe support boundaries for public interview and offer links.

Confirmed implementation​

Public endpoints look up interviews/offers by token and accept feedback or terminal offer responses. Duplicate terminal offer response is idempotent.

Safe operational guidance​

Confirm only route category and record state. Never copy, log, transmit, or request token values. Escalate lookup or exposure concerns.

Signals and evidence​

Invalid/unresolved-link category, terminal offer state, duplicate-response behavior, and safe correlation evidence.

Risks and escalation​

Token strength, authentication, expiry, revocation, rotation, replay protection, rate controls, redaction, and incident process require confirmation.

Source References​

  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Application/Compatibility/CompatCommands.cs
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrSuitePage.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.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

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