Recurring Certifications
How Zluri handles recurring access certifications
While creating access certifications, you can set them to recur at fixed intervals such as monthly, quarterly, or custom durations up to 12 months. This article explains how Zluri handles these recurring certifications.
Zluri uses the Review start date of the first certification as a reference point for future schedules. Intervals between review and remediation end dates stay consistent.
Say a certification has the following schedule:
- Review start date: 01 Jan 2025
- Review end date: 15 Jan 2025 (14 days from review start)
- Remediation end date: 20 Jan 2025 (5 days from review end)
The upcoming instances will follow this schedule:
Instance | Review start date | Review end date | Remediation end date |
---|---|---|---|
1 | 01 Jan 2025 | 15 Jan 2025 | 20 Jan 2025 |
2 | 01 Feb 2025 | 15 Feb 2025 | 20 Feb 2025 |
3 | 01 Mar 2025 | 15 Mar 2025 | 20 Mar 2025 |
4 | 01 Apr 2025 | 15 Apr 2025 | 20 Apr 2025 |
5 | 01 May 2025 | 15 May 2025 | 20 May 2025 |
Accounting for month-end dates
There might be cases where the Review start date doesn’t exist in the following month, (for example, if you choose 31 January, which doesn’t exist in shorter months like February and April).
Assume a certification with the following schedule:
- Review start date: 31 Jan 2025
- Review end date: 15 Feb 2025 (15 days from review start)
- Remediation end date: 20 Feb 2025 (5 days from review end)
Here, Zluri will automatically adjust the start date to the last day of that month (28 February or 30 April). Everything else stays identical:
Instance | Review start date | Review end date | Remediation end date |
---|---|---|---|
1 | 31 Jan 2025 | 15 Feb 2025 | 20 Feb 2025 |
2 | 28 Feb 2025 | 15 Mar 2025 | 20 Mar 2025 |
3 | 31 Mar 2025 | 15 Apr 2025 | 20 Apr 2025 |
4 | 30 Apr 2025 | 15 May 2025 | 20 May 2025 |
5 | 31 May 2025 | 15 Jun 2025 | 20 Jun 2025 |
Got questions? Feel free to submit a ticket or contact us directly at [email protected].
Updated about 3 hours ago