I created a certification campaign with an end date configured. After the campaign reached its end date, I noticed that the campaign remained active and the certifier was still able to make decisions on the certification items.
Based on my understanding of the documentation, once the campaign end date is reached, certifiers should no longer be able to make decisions, even if the campaign itself remains active.
Could you please confirm whether this behavior is expected?
If it is expected, could you clarify what the campaign end date controls and how I can prevent certifiers from making additional decisions after that date?
This is the expected behaviour that campaigns do not get autocloses until there is a control in place.
You will need to close the campaign either by maintaing or revoking the access per your configuration to make reviewers unable to attempt the campaign at Admin—> certification—> campaigns —> Active.
So, what is the purpose of the campaign end date if the certifier can still make decisions after the date has passed?
I understood that the end date should define the point after which certifiers can no longer take action on the certification items. Could you please clarify what functionality the campaign end date actually controls?
With my understanding, the purpose of keeping the campaign active is to give certification administrators grace period to take an effective decision as per their enterprise compliance to close the campaign or to assign those to oneups or security officers.
And to answer your question is regarding the end date in SailPoint ISC acts purely as a target timeline and a deadline indicator.
if you want to take action on the active campaigns after due date you can click the Actions dropdown menu next to it and select Complete & Revoke Access (or Complete & Maintain Access, depending on your organizational requirements and policy for undecided items).
What it functionally controls is two things. First, it drives the automatic Certification Due reminder emails that ISC sends every seven days until the reviewer signs off or an admin completes the campaign. The deadline date is what appears in those reminders. Second, the Complete action only becomes available after the campaign has passed its deadline. The Complete Campaign API also returns a content error if the campaign is not yet past due.
The Completing a Campaign docs actually list “wait for reviewers to complete their decisions” as one of the supported post-deadline options. So the behavior you are seeing is intentional.
To stop decisions after the deadline, the campaign has to be explicitly completed. You can do this from Admin > Certifications > Campaigns using the Actions menu (Complete, Complete & Maintain Access, or Complete & Revoke Access, depending on how you configured the undecided items setting during campaign creation).
If your compliance policy requires a strict automatic cutoff at the deadline, you would need a scheduled workflow that calls the Complete Campaign API with the autoCompleteAction parameter. That API only succeeds for campaigns that are already past due. The default behavior maintains access for undecided items unless you explicitly set autoCompleteAction to REVOKE.
