> ## Documentation Index
> Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Credential Requirements

> Manage which credential types are required for specific positions and departments.

The Credential Requirements page manages the mapping of credential types to positions and departments. It is available at route `/hr/credential-requirements`.

## Overview

The page fetches credential requirements from `useCredentialRequirements`, optionally filtered by `positionId` and `departmentId`. Two filter dropdowns (Department, Position) allow scoping the list. Each requirement card shows the credential type and the associated position or department. Users with the appropriate permission can delete a requirement using the trash icon, which opens a confirmation dialog. A "+" button opens the form for adding new requirements.

## Who it's for

Access follows your organization's role and module configuration. Data is scoped to the current organization.

## Before you start

* Credential types must be defined at `/hr/credential-types` before creating requirements.
* Positions and departments must exist for position- or department-scoped requirements.

## Steps

<Steps>
  <Step title="Open Credential Requirements">
    Navigate to **HR → Credential Requirements** or go to `/hr/credential-requirements`.
  </Step>

  <Step title="Filter by Department or Position">
    Use the Department and Position filter dropdowns to narrow the displayed requirements.
  </Step>

  <Step title="Add a requirement">
    Click the **+** button to open the requirement form and link a credential type to a position or department.
  </Step>

  <Step title="Delete a requirement">
    Click the trash icon on a requirement card. Confirm deletion in the dialog that appears.
  </Step>
</Steps>

## Related

<Columns cols={2}>
  <Card title="Human Resources" icon="users" href="/hr/overview">
    Human Resources core overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index" />
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/hr.tsx
  * src/cores/hr/pages/CredentialRequirements.tsx
  * src/cores/hr/hooks/credentialing/useCredentialRequirements.ts
</Accordion>