Skip to main content

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.

The Credential Types page manages the catalog of credential type definitions used when assigning credentials to employees. It is available at route /hr/credential-types.

​
Overview

The page fetches credential types from useCredentialTypes. Each type card displays the credential name and a category badge. Category values visible in the code: license, certification, training, compliance, background_check, and a default fallback. Each badge uses a distinct semantic color token. A + button opens CredentialTypeFormDialog for adding or editing a type. A Seed Defaults button (with sparkle icon) calls seedDefaultTypes to populate an initial set of credential types for new organizations.

​
Who it’s for

No explicit permission gate on this route. Data is scoped to the current organization.

​
Before you start

  • For a new organization, use Seed Defaults to populate a starting credential type catalog before creating credential requirements or assigning credentials.

​
Steps

1

Open Credential Types

Navigate to HR → Credential Types or go to /hr/credential-types.
2

Seed default types (new org only)

If the list is empty, click Seed Defaults to populate a standard starting set of credential types.
3

Add a credential type

Click + to open the form dialog. Enter the type name, category, and any other required fields.
4

Edit an existing type

Click a credential type card to open it for editing in the dialog.

​
Key concepts

  • Category — Classifies the credential type: license, certification, training, compliance, background_check. Category drives the badge color on cards and may filter views elsewhere.

Human Resources

Human Resources core overview.

Governance & parity

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.
  • src/routes/hr.tsx
  • src/cores/hr/pages/CredentialTypes.tsx
  • src/cores/hr/hooks/credentialing/useCredentialTypes.ts