The credential vault now decides expiration the same way a person would
The vault picks a credential's current version based on what the document itself says — not upload order — and agencies can now set their own validity windows so the system applies them automatically.
Two related problems made a credential's status less trustworthy than it should be.
The first was about which copy of a document counts as current. Until now, the vault treated whichever file arrived first as authoritative, and corrected course only once an AI review caught the mistake. Upload an old copy of a certification before the new one syncs in, and the credential could read as expired even though a valid copy existed. Now the vault waits for real information — a stated date, a verification result — before deciding which version is current, and a stated expiration date always wins over one the system merely inferred from a scan.
The second is about how long evidence stays good. Rules like "a background check is valid for 30 days" used to live only in a policy document that no agent could actually read. Your team can now set that validity window once, for a specific requirement, and every agent applies it automatically — including working out an expiration date for a document that doesn't print one at all.
See it work a real file.
Thirty minutes, one placement, worked live — start to submit-ready.