A credential is not affecting status
Why a credential you entered is not closing a gap or clearing an action item.
It is mapped to Custom / Other
This is the most common cause. Custom / Other records are tracked for expiration but match no catalog credential type, so they cannot satisfy a requirement.
- 1Confirm the catalog contains the credential type under Requirements → Credential Types.
- 2Edit the credential and select that catalog type.
- 3Re-check the employee's requirements section.
The Requirements page surfaces unmapped credentials — records entered as Custom / Other that may belong to a catalog type.
No requirement exists for that type
A credential with no matching requirement is tracked for expiration but never affects requirement status, the matrix, or Autopilot. If the employee shows No Requirements, no role template or direct requirement applies to them at all.
The credential is archived
Archived credentials do not contribute to compliance. Check the archived section of the profile.
The employee is archived
Archived employees drop out of active views, counts, and compliance calculations entirely. Reactivate them if they are still employed.
Autopilot has not run yet
Scheduled work runs on its own cadence. A change you make now is picked up on the next run rather than instantly. Derived status, by contrast, updates immediately.