Skip to main content

Public Offer Response UI

Purpose​

Lets a candidate retrieve an offer by public token and accept/sign or reject it.

Public offer token route; no protected-route wrapper.

Intended users and preconditions​

The candidate or recipient possessing the public link. The token must resolve to an offer record.

Main components​

Offer summary, signer fields, accept/sign action, rejection-reason flow, status-sensitive disabled state, and error messaging.

Fields, columns, and sections​

Source-defined signer/signature and rejection-reason inputs are present. Offer and compensation values are intentionally not copied into this documentation.

Filters and actions​

Accept/sign or reject. Existing accepted/signed/rejected states disable duplicate acceptance in the UI.

Validation​

A rejection reason is required by the page. Server-side token and transition rules are authoritative.

UI states​

  • Loading: Token lookup occurs on mount; dedicated skeleton evidence is limited.
  • Empty: Invalid or expired links render an error.
  • Success: The UI records terminal response state and prevents repeated acceptance through its disabled condition.
  • Error: Invalid/expired lookup and response failures are displayed safely.

Permission behavior​

Possession of the route token is the visible access mechanism. Authentication strength, expiry, revocation, replay protection, and identity binding require confirmation.

API dependencies​

Uses public offer lookup, sign, and reject endpoints.

Public terminal responses are idempotent in service behavior. Token values must never be logged or included in support evidence.

Screenshot placeholder​

Capture only sanitized, non-production data after product and privacy review. No screenshot is embedded in this Draft page.

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOffersPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrSuitePage.tsx
  • microservices/src/recruitment-service/Application/Commands/OfferCommands.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