Employer users can already access anonymised CVs without sending a contact request, such as the job preferences, education, work experience, languages and skills. However, if the employer would like to access the personal information of a candidate (e.g. name, birth date, current location, phone number, email address), the applicant user first has to approve access.
The title of a CV is based on the desired job title and not on the applicant's name as personal contact information is only revealed for users who sent a contact request. Not only does this logic prevent users from searching the applicant's name on search engines to get the contact details for free, and thus, tries to circumvent the contact request workflow. Based on the data privacy regulations of the country where your job board is situated, the approval of the applicant user may also be a legal necessity.
Whereas employers can access anonymous CVs by default, the personal information of a CV is only shown after the contact request has been approved by an applicant user.
If the employer user is interested in a CV and requires access to personal contact information, a contact request (or invitation) must be submitted to the applicant user. The applicant user then obtains an email with the invite and can either confirm or deny the request. If the request was confirmed, the system automatically sends the employer user an email to inform the user that the CV can now be accessed.
Contact requests and company groups
For companies that operate using the group module, contact requests will always be assigned and sent out on behalf of the company that the user has active at that moment (in the company switcher in the sidebar).
This means that if a parent company issues a contact request on behalf of a child company, only members of the child organization will have access to the resume (once the contact request has been accepted). An employer user of the parent company can also access the resumes that child organizations have access to, provided that they have the respective child organization active in the organization switcher.
- When a company (child or parent) issues a contact request, only the current organization the user has active at that moment gets access to the resume
- Sibling child companies (and parent companies) can make contact requests to the same user
Example:
Parent company = Company A
Child company 1 = Company 1
Child company 2 = Company 2
- Each company can send out a separate contact request -> every company has then access to the resume
- The parent company (Company A) can send out a contact request on behalf of Company 1 -> only Company 1 will have access to the resume