Two consent types operate in the interface, and they differ in how long they let you keep data.
Consent for this recruitment
Allows processing the candidate's data for one process. It has an expiry date, counted according to your GDPR settings.
Consent for future recruitments
Allows you to come back to the candidate for later projects. This is what makes the candidate database useful as a source — without it you may not contact the person once the process ends.
Where to see consent status
on the candidate profile, in the Consents tab,
on the candidate list, if you add the relevant column,
in the consent filter, where you can find people whose consent is about to expire.
You turn on the "GDPR" column in the "Columns" menu above the candidate list. Hover over the dot to see the consent state.
Where consents come from
Usually from the application form — the candidate ticks them when submitting. When adding a candidate manually you choose the consent yourself, and it is a required field.
You open the add candidate window with the "Add candidate" icon in the top bar. The consent choice is in the "GDPR consents" section.
Expiry reminders
The system can email a candidate about a consent nearing its end. Note that it is an informational message — it contains no one-click button to extend the consent.
You set up this message in Settings, under "Automatic emails". Click "Add automatic email", in "Sent when" choose "Expiring GDPR consent" and enter "Days before consents end".
