Skip to main content

Recruitment Permissions and Governance Reference

CapabilityAuthentication / tenantUI visibilityNative APICompatibility APIScope evidencePublic/document behaviorMaturity / confirmation
Protected workspace/readClient authentication and tenant contextRecruitment feature and recruiter/HR-oriented hintsNo explicit endpoint policyNo explicit endpoint policyOwnership/manager scope absentDocuments may be exposed through workspace actionsTransitional; authoritative enforcement required
Manage openings/candidates/interviews/offers/onboardingProtected UI; backend tenant required where command uses contextSame coarse feature guardNo per-capability policyNo per-capability policyRecruiter/HR/hiring-manager/interviewer scopes unconfirmedCompensation, notes, KYC, and documents need finer controlsRequires confirmation
Requisition decisionTenant context; Workflow mode may restrict direct decisionNo dedicated UINo explicit policyNo dedicated compatibility decision UIApprover identity and separation of duties incompleteNot publicTransitional
Compensation approval / offer approvalProtected UI for candidate CTC; native offer APIs existNo separate action permissionNo explicit policyNo separate enforcement evidenceThresholds and self-approval restrictions absentCompensation boundary requires governanceRequires confirmation
Public applicationPublic route/endpointsPublic CareersPublic native/compatibility surfacePublic compatibility surfaceCandidate scope by submitted openingResume upload; consent/retention unconfirmedTransitional
Public feedback/offer responseOpaque route tokenPublic token routePublic endpoints existPublic compatibility endpointsInterviewer/candidate binding unconfirmedToken and sensitive content riskRequires confirmation
DocumentsProtected/public depending actionEmbedded actions onlyNo explicit document permissionCoarse Recruitment routePer-document ownership absentDownload and content access need governanceRequires confirmation
Workflow callbackService callback routeNo UINo explicit callback policyN/ACaller trust unconfirmedNot public UIRequires confirmation

The backend policy catalog is empty. UI roles/features influence visibility but do not prove authoritative authorization. Platform entitlement enforcement, final role catalog, segregation of duties, and audit-access policy require confirmation.

Source References​

  • microservices/src/recruitment-service/Api/Policies.cs
  • microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
  • microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
  • microservices/src/recruitment-service/Api/RecruitmentPublicEndpoints.cs
  • UI/salary-ui/apps/client-hrms-portal/src/utils/ProtectedRoute.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/components/AppLayout.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