Concept: Neutrality and Privacy Settings

Neutrality and privacy settings enable users to control when specific candidate information displays during the sourcing and selection process. This can minimize unintentional bias and ensure candidates are chosen based on their skills rather than vendor relationships or personal demographics. Neutrality and privacy settings can also help organizations comply with regional data privacy and anti-bias regulations.

Administrators can create rules to obscure sensitive candidate Personally Identifiable Information (PII) from specific security roles until an applicant transitions to a designated stage in the hiring or work order lifecycle. Example: Hiding a candidate name from a hiring manager until the candidate reaches the

Ready to Onboard

status.

The feature consists of two parts:

Vendor Neutrality
: The practice of hiding vendor identifying details from resource managers or other client users to eliminate vendor bias during candidate review.
Candidate Data Masking
: Obfuscating specific data points such as email, phone number, and address. Candidate name fields are replaced with a system-generated unique identifier.

In order for a masking rule to restrict where a role can see specific data points, the role must first have the relevant base permission for those data points. The created rules subsequently restrict when those permissions are active and when they are not.

When a rule is active, impacted users experience the following behavior changes across the application:

Feature	Masking Rule Result
Candidate Full Names	Replaced by a system-generated unique identifier across Job Application pages, Statement of Work , Profiles, and lists.
Candidate Fields	Data is hidden across these areas: Card details on the Job Applicant List Job Candidate Application page Job Candidate Application Checklist tab Job Candidate Work Order page Card details and the Scheduling modal on the Job Interview List Work Order List page Work Order page Offer Onboard Card details on the SOW Teams List Card details on the SOW Role Applicant List SOW Candidate Application page SOW Candidate Application Checklist tab SOW Candidate Work Order page Notifications Approvals & Tasks When data is hidden, a lock icon and a Hidden label displays. If no data is present, a No Data label displays.
Vendor Exposure	Vendor details are hidden across: Job Applicant List Job Candidate Application page Job Candidate Application Checklist tab Job Candidate Work Order page Job Interview List Work Order List page Work Order page Offer Onboard Notifications Approvals & Tasks Activity Logs When data is hidden, a lock icon and a Hidden label displays. If no data is present, a No Data label displays.
Automated Reveal	Once a candidate transitions out of the configured criteria, candidate information and vendor details automatically populate in the UI.

Once a rule has been saved, VNDLY removes the applicable permission from the defined security role and automatically creates a child role under that security role that awards the permission only for scenarios that follow the rule’s definition using Security Work Order Policies. It is very important that the relevant permissions are not manually added back to the primary security role. This renders the rule moot, as that role will again have the permission across the entire application.

If a rule is ever made inactive on the

Neutrality and Privacy Settings

page, VNDLY automatically adds the relevant permissions back to the primary security role.