An employee shows as non-compliant unexpectedly

Work through these in order. The first two account for most cases.

1. Check the credential type

A credential satisfies a requirement only when it is mapped to the same catalog credential type. A record entered as Custom / Other will not close a requirement for a catalog type, even if the name looks identical.

1. 1Open the employee's profile.
2. 2Compare the credential's type against the required type in the requirements section.
3. 3Edit the credential to use the correct catalog type if they do not match.

2. Check the expiration date

An expiration date in the past makes the credential expired regardless of how recently it was entered. A typo in the year is the single most common cause.

3. Check where the requirement came from

The profile shows which role template or direct requirement calls for each credential type. If a requirement is unexpected, an assigned role is probably the source.

• Remove the role if it no longer applies to this person.
• Remove the direct requirement if it was added in error.
• Edit the role template if the requirement is wrong for everyone holding that role.

4. Check the credential is not archived

Archived credentials appear in a separate section on the profile and do not contribute to compliance. Reactivate it if it was archived by mistake.

5. Check the warning window

Expiring soon means within thirty days. A credential valid for three more weeks is genuinely expiring soon, not mis-flagged.