ATS Pro Development / Feature Requests logo

ATS Pro Development / Feature Requests

Tell us how we can make ATS Pro (Bug Report) better!

Submit Feedback
1

Feature Request / Clarification: GDPR Consent Management, Candidate Search and Bulk Email

Question:

Does this functionality already exist, or could it be implemented?

We need an effective way to identify candidates who have not yet provided GDPR consent and send them GDPR consent requests in bulk.

Currently, the system displays consent-related statuses such as No Consent – 763 Candidates and Needs Attention.

While this information is useful, displaying numbers alone does not actually help us resolve these issues.

1. Clickable GDPR Statuses

Could these GDPR statistics become clickable links, opening a filtered list of the exact candidates associated with each status?

For example:

  • No Consent – 763 → Display all 763 candidates without consent.

  • Needs Attention → Display the candidates requiring attention.

  • Other GDPR statuses → Display the corresponding candidate lists.

This would allow us to identify the affected candidates immediately and take corrective action rather than knowing an issue exists without knowing who it affects and how to fix it.

2. GDPR Consent Emails – Bulk Sending

We need the ability to search and filter candidates who:

  • Have no GDPR consent recorded.

  • Have never received a GDPR consent request email.

  • Require a GDPR consent renewal or further action, where applicable.

Once identified, we should be able to select candidates individually or in bulk and send them the appropriate GDPR consent request directly from the filtered results.

3. GDPR Compliance / Activity Log

The existing activity log appears extremely basic.

Seeing that a particular user accessed or deleted a candidate profile at a specific date and time provides limited compliance value without meaningful details about the actual action performed.

Could this be expanded to provide more meaningful audit information, including specific actions, changes made and relevant GDPR consent/email history?

Ultimately, the objective is straightforward:

We need to identify GDPR issues, locate the affected candidates, take corrective action and manage consent requests efficiently.

Currently, the system tells us that problems exist, but does not provide an effective way to identify and resolve them.

The underlying data is already there; what is missing is the functionality to actually work with it.

O Ovi · 22h ago
Pending