Consent Admin Setup

The following parameters need to be set up in SFDC for Double Opt-in and Remote Consent to work as expected

Pitcher Consent Management Settings

The following fields inside Custom Metadata Object need to be filled:

Label -> System Setting
Pitcher Consent Management Setting Name -> System_Setting (the following value must be created as defined in the screenshot to work.
Remote Consent: Custom Email Template -> create a Classic Email Template and include API name here to be used as Remote Consent Email Template.
Remote Consent: Custom Reminder Template -> create a Classic Email Template and include API name here to be used as Remote Consent Reminder Template. (It can be the same template defined as the first email).
Remote Consent: Pending Status -> Remote Consent Pending should be the default status, but custom status can be defined.
Remote Consent: Completed Status -> Completed should be the default status, but custom status can be defined.
Remote Consent: Expired Status -> Remote Consent Expired should be the default status, but custom status can be defined.
Remote Consent: Reminder Iteration -> Define Reminders Emails to be sent to customers. 0 means no reminders will be sent.
Remote Consent: Enable Multi-Lang Email -> if the checkbox is set up as true, Remote Consent Multi-Lang Email Config Custom Metadata will be checked to define Language Template to be used. By default will be checked values are defined inside these settings.
Double Opt-in: Custom Email Template -> create a Classic Email Template and include API name here to be used as Double Opt-in Consent Email Template.
Double Opt-in: Custom Reminder Template -> create a Classic Email Template and include API name here to be used as Double Opt-in Consent Reminder Template. (It can be the same template defined as the first email).
Double Opt-in: Pending Status -> Double Opt-in Pending should be the default status, but custom status can be defined.
Double Opt-in: Completed Status -> Completed should be the default status, but custom status can be defined.
Double Opt-in: Expired Status -> Double Opt-in Expired should be the default status, but custom status can be defined.
Double Opt-in: Reminder Iteration -> Define Reminders Emails to be sent to customers. 0 means no reminders will be sent.
Double Opt-in: Enable Multi-Lang Email -> if the checkbox is set up as true, Double Opt-in Multi-Lang Email Config Custom Metadata will be checked to define Language Template to be used. By default will be checked values defined inside this setting.
Account: Custom Email Field -> Define what is your Account Email inside your SFDC org.
Person Account: Custom Email Field -> Define what is your Person Email inside your SFDC org.
Contact: Custom Email Field -> Define your Contact Email inside your SFDC org.
Send Email Reminder In -> Define the period time for the first reminder.
Send Email Reminder Iteration in -> Define period time between 2nd Reminder Email.
Disable Sending Consent Email -> Allow to disable sending emails to customers and use your Email communication Tool connected to SFDC.
Disable Sending Consent Reminder Email -> -> Allow disabling sending reminders emails to customers and use your Email communication Tool connected to SFDC (this setting only works for the user executing the batch and can be considered org wide setting).
User: Custom Field Remote Consent Name -> Custom Field on User Object for Multi-language Remote Consent Setting Name.
User: Custom Field Double Opt-In Name -> Custom Field on User Object for Multi-language Remote Consent Setting Name.
Overview Send by Email? -> Allow to set up Send Email toggle to customers by default on/off.
Remote Consent: Enabled -> Allow to enable Remote functionality inside consent UI.
Reminder Email -> Allow to set up Org Wide Email Address.
Disable Account Selection -> Account selection will be greyed out, and not possible to collect consents to Accounts, so only Contacts.
Disable Consent Outside Engagement -> F2F Consent will be only possible inside a call. Consent should still be possible to Save as a Draft or collect via Remote.

Double Opt-In Multi-Lang Email Config

The following fields inside Custom Metadata Object must be filled to enable multi-language email templates for Double Opt-in Consent.

Label -> Language like English or French
Double Opt-In Multi-Lang Email Config Name -> Languages like English or French.
Email Template Name -> create a Classic Email Template and include the API name here to be used as Double Opt-in Consent Email Template.
Reminder Template Name -> create a Classic Email Template and include the API name here to be used as Remote Consent Reminder Template. (It can be the same template defined as the first email).

Remote Opt-In Multi-Lang Email Config

The following fields inside Custom Metadata Object must be filled to enable multi-language email templates for Remote Consent.

Label -> Language like English or French
Double Opt-In Multi-Lang Email Config Name -> Languages like English or French
Email Template Name -> create a Classic Email Template and include the API name here to be used as Double Opt-in Consent Email Template.
Reminder Template Name -> create a Classic Email Template and include the API name here to be used as Remote Consent Reminder Template. (It can be the same template defined as the first email).

Enable Multi-language templates by Market

As part of the new package version 1.52, new functionality has been introduced to create multiple Email template combinations based on Market - Languages specifications. The following steps need to be set up to enable that functionality:

Go to Pitcher Consent Management Settings Custom Metadata.
Add field to be used as the value for User: Custom Field Remote Consent Name like "Country".
Go to Double Opt-In Multi-Lang Email Config Custom Metadata.
Create a new value with the new combination like English-Canada or English-US.
Add the correct template name.
Repeat steps for Remote Consent Multi-Lang Email Config Custom Metadata.

Note: the correct order will always be Language-User field value like English-US or English-UK.

Enable Multiple Pitcher Consent Management Settings

As part of the new package version 1.53, the following fields inside Custom Metadata Object need to be filled to enable wide settings for the user and provide different Consent Metadata settings for each type of user or market.

Label -> System Setting
Pitcher Consent Org Wide Settings Name -> System_Setting
User: Custom Field for Consent Setting -> add API name of the field of the user object, which is used to get record from Picher consent management Settings.

Create a new Pitcher Consent Management setting based in the Market, like in that case of Country

Add Default Channel values used in the Consent Form

As part of the new package version 1.54, the following fields inside Custom Metadata Object need to be filled to retrieve channels values from SFDC to Consent Form

Label -> System Setting
Pitcher Consent Org Wide Settings Name -> System Setting
Account: Custom Channels field -> add API name of the field of the account object, which is used to get channel value in the Picher consent form
Contact: Custom Channels field -> add API name of the field of the contact object, which is used to get channel value in the Picher consent form

Add Default Reminder Batch: Days Record Old

As part of the new package version 1.59, the following field inside Custom Metadata Object must be filled to retrieve the Consent logs record modified in the last n days to be part of Consent Reminder logic. The default value is 5

Label -> System Setting
Pitcher Consent Org Wide Settings Name -> System Setting
Reminder Batch: Days Record Old -> 5

Add Org Wide Email Addresses

If your organization's email address is available and verified

Note: if the reminder email is empty and Organization-Wide Email Addresses are not set up, emails will be sent to the user that has scheduled the job SCB_ConsentReminder.