Postponed (maintainer needs more info)
Project:
Drop Jobs
Version:
7.x-1.x-dev
Component:
Candidate Feature
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
1 Jul 2012 at 01:16 UTC
Updated:
23 Jun 2013 at 14:34 UTC
Comments
Comment #1
alexweber commentedComment #1.0
alexweber commentedupdated contents
Comment #2
alexweber commentedI'm not sure about this one anymore. Whereas I agree that there should be some way to respect candidates' privacy, it IS a job search website and if recruiters can't see parts of their resume, then what's the point of even including this data?
As a side-note, we're now using Field Permissions on all resume fields so site builders can change this as they see fit for their use case.
Allowing candidates to control visibility for every field would mean implementing something complex and totally custom which would have to wrestle with Field Permissions and other access control in order to achieve this and I'm just not comfortable with this.
Also, I have an idea for subscriptions based on a previous job website I built where by default only certain resume fields are visible, and employer need to have an active (paid) subscription to reveal the extra fields. This would be totally doable using the Subs Roles submodule that ships with Subs.
All of that said, I'm leaving this issue open in case anyone stumbles upon it and wants to chip in.
Comment #3
dargente commentedProfile2 Privacy does exactly this. I haven't explored all of dropjobs yet since i just installed and encountered bunch of Strict Warning and Menu Router errors, but I see Profile2 as a module being used. As long as the 'Profile' is separated from the account page and is the actual resume, then admin will be able to specify privacy settings like 'None' 'Hide Name & Organizations' 'Connections Only' or whatever. Profile2 Privacy allows you to specify which fields are shown to which roles based on the user's choice of privacy setting.
Comment #3.0
dargente commentedfixed formatting