You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Candidate Deactivation vs Deletion GDPR

edited Feb 25, 2021 10:58AM in Taleo Enterprise 1 comment

Summary

Should we remove the ability to deactivate to avoid confusion?

Content

Hi everyone,

I wanted to get your thoughts on how you are managing candidate deactivation vs deletion in relation to GDPR. We have had a few cases where a candidate has deactivated their account thinking that it is deletion. In some situations we have had to go and find their deactivated profile, reactivate it and then fully delete. Is this confusing for a candidate having the option to deactivate themselves vs contact our data protection officer for full deletion? Has anyone turned off the ability to deactivate?

Thanks,

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!