Example 1:
Candidate Josef applied for the PHP Programmer (Senior) position. During the recruitment process, we find that Josef fits our team perfectly, but doesn't have the required senior skills, but fortunately we have an open offer for PHP Programmer (Junior). We reject the candidate for the senior position because he doesn't have the required knowledge/experience and we copy him from the Senior position to the PHP Programmer (Junior) position. All information obtained so far, connected with the PHP Programmer (Senior) position, i.e., interview notes, notes, history, etc., remain on the candidate card under this position.
Example 2:
Candidate Josef previously applied for a historical position, was not accepted, but was a capable applicant whom we kept in the database. In case a position for which candidate Josef would be suitable appears in the future, we copy the candidate to that new position. All information obtained so far, connected with the previous position, i.e., interview notes, questionnaires, etc., remain on the candidate card, only in the tab of that historical position.
Example:
Candidate Josef accidentally applied for the Warehouse Worker position instead of Warehouse Manager. So we move candidate Josef to the correct Warehouse Manager position before we work with him in any way. All information connected with the Warehouse Worker position will disappear.
You can find these two actions on the candidate card or in bulk actions on position detail.
You can also find the "Copy candidate to another position" action in the candidate database.
This action allows you to copy a candidate to multiple positions, so select positions, then attachments you want to copy to the selected positions, and if you want to keep the response source from the current position, just check this option. If you don't select the last option, this value will automatically be "Recycling: From database".
Copying a candidate can be done by one of these options:
In other words, you choose whether you need to inform the candidate about the new position offer via email and ask them for GDPR consent for placement in the given position. In both cases, the candidate's application for the given position is created, but in the "with email" scenario, it is unconfirmed from the personal data processing consent perspective for the given position. You cannot work with the candidate on the position until the confirmation takes place - either by the candidate (button in the sent email) or by the recruiter (thumbs up button from the recruiter's side).
As mentioned, when copying a candidate, we keep all information that we have obtained so far within historical positions. Information for specific positions can be found in the tabs of the given specific position under the candidate's name.
This action allows you to move a candidate from position A to position B.
Before the move actually takes place, you will be warned about the loss of interview notes and questionnaire. What does this mean? All information connected with the previous position will be removed and the only position tab will be the one you just moved the candidate to.
Settings required to display candidate name on incoming calls for iOS and Android devices.
What can our brand new version of the mobile app do?
The mobile app is periodically logged out for security reasons