[Role Management] create a type of member who only sees resumes and never sees existing internal notes or those of other members.
B
Beryl Egret
We would like to know if it is possible to set up a specific configuration for this type of member, with the following rights:
access only to candidate CVs,
possibility to add notes,
without access to internal notes already existing or added by other team members (admin and/or manager).
The objective is to allow the Tech Lead to participate in the evaluation of profiles (feedback on technical tests) while maintaining the confidentiality of our internal exchanges on the recruitment side.
Purpose: create a type of member who only sees resumes and never sees existing internal notes or those of other members.
Log In
P
Pauline Caillot
Hello Beryl Egret,
Thanks for your suggestion 😊
The need you describe (allowing a Tech Lead to consult CVs and submit feedback, without having access to existing internal notes) corresponds precisely to a use case that we are already addressing via our candidate sharing feature.
Thanks to the sharing settings, you can:
Give access only to the required elements (CV, cover letter, form responses, etc.)
Allow access to the note space in order to allow the addition of feedback, without giving access to existing internal notes or their history
Thus, the Tech Lead can assess the candidate and write his own feedback, without visibility on previous internal exchanges.
It is also possible to share en masse from the CV library or Kanban, in order to transmit a complete pool of candidates to consult.
We understand that this need could also be part of a finer evolution in role management. To date, the collaborative logic of internal members (admin, manager, collaborator) implies by default a certain transparency between them. It is precisely to respond to cases like yours that the sharing feature was designed: to allow targeted and compartmentalized collaboration.
👉 However, we keep your suggestion in our areas for improvement concerning role management.
In the meantime, the sharing feature remains the most suitable solution to move forward without blocking.
I added a screenshot of the various views (Flatchr member vs sharing interface).
Do not hesitate to contact support@flatchr.io if you wish to be accompanied in the configuration 🙂