Each type has a validity period in days, applied when a check passes. Zero means it never expires. The supplied defaults are 730 days for identity and age checks and 365 days for affiliation checks.
Choosing a period
Base it on how quickly the fact stops being true. Students graduate and staff move on, so an affiliation check should be revisited. Someone who was over eighteen two years ago still is, so a long period — or none — is perfectly defensible for an age check.
Expiry takes effect immediately
A lapsed pass stops counting the moment it lapses, not whenever a scheduled task next runs. There is no window in which an expired verification still grants a discount.
The nightly housekeeping
- Lapsed passes are marked expired, so the record is honest and your automation is notified once per lapse.
- Checks sitting with the user for more than 72 hours are cancelled as abandoned.
Both work in batches, so a large backlog clears over several nights rather than all at once.
Re-verification
Allow re-verification decides whether a user may try again after a rejection. Leaving it on is usually right — rejections happen for mundane reasons such as a blurred photograph, an expired document or a mistyped address, and a customer with no way back is a support ticket.
Switch it off only where a repeated attempt is itself something you want to prevent, and understand that you are creating a dead end only an administrator can reopen.
Expired is not rejected
Somebody whose pass has expired previously satisfied the check. Say this needs renewing, not you failed.
Worked Examples
- Annual student discount: 365 days, so it naturally re-checks each academic year.
- Age gate: validity zero — the fact does not stop being true.
- Contractor access: 90 days, matching the contract review cycle.