Create Consent Types (Salesforce Classic)

Note: To take advantage of the features mentioned in this documentation, your Org needs to be using (Undefined variable: bh4SFVersions.Latest Package Version) or newer. See Release Notes for more details about which features were introduced in each release. If you would like to upgrade to the current release, contact Bullhorn for Salesforce Support.

Overview

ConsentClosed In BH4SF , Consent is used in the context of GDPR or similar data privacy processes. Candidates or Clients are usually asked to consent to the storage or sharing of their personal data. Type is a Bullhorn for Salesforce package object. Consent Types are not configured by default but instead each Salesforce Org configures their own, according to local requirements and business needs. This article shows you how to create Consent Types.

GDPRClosed General Data Protection Regulation is a set of rule enacted by the EU to further protect candidate / contact informtion and provide them control over their own information. is one of the types of consent that you can create. According to GDPR, if two types of consent are requested in a single email but one of the consent types is declined, the refused consent overrules the approved consent on the other type. In such cases, consent has not been given so we recommend sending separate emails for each type of consent.

Create Consent Types

Follow these steps to create new Consent Types. Once the Consent Type is created, you have the option to either manually or automatically send consent emails to new ContactsClosed A contact (or client contact) is the person who the recruiter is working with at a Company. In Talent Rover a Contact can be either a Client Contact or a Candidate Contact. Both types of Contacts are stored in the same object (Contact)..

  1. Navigate to Consent Type.
  2. Click on New.
  3. Enter the Consent Type Name, Email Body, and Language.
  4. Choose if this Consent Type will be the Default.
    • The Default will be the Consent Type sent to new contacts. At least one Consent Type must be marked as true. Multiple Default Consent Types are also supported.

Admin Note:

To make sure theConsent Type is tracked correctly when sending and receiving consent responses from candidatesClosed A person looking for a job. A candidate can also be referred to as a Job Seeker, Applicant, or Provider., update these two Contact fields as part of the initial implementation and every time you add or remove a Consent Type or change the name of an existing one.

TR1__Consent_Types__c

  • The values in this multi-select picklist should correspond to the names of the Consent Types in use in the Org

TR1__Consent_Type_Response_Status__c

  • The values in this multi-select picklist should correspond to the names of the Consent Types in use in the Org along with the Response Status. These are case sensistive. For example:
  • ConsentType1 - Not Responded
    ConsentType1 - I Consent
    ConsentType1 - I do not Consent
  • ConsentType2 - Not Responded etc...