To configure this feature:

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the permission set for the appropriate user profile.
4. Navigate to Objects.
5. Grant the following permissions:

   Object	Object Types	Object Permissions	Fields	Field Permissions
   multichannel_consent__v	n/a	n/a	sent_email__v consent_confirm_datetime__v related_transaction_id__v	Edit
   multichannel_message__v	double_opt_in__v	Read	consent_confirm_html_file__v html_message_file__v message_identifier__v name__v object_type__v	Read
   multichannel_route__v	n/a	Read	approved_document__v country__v default__v language__v object__v record_type_name__v vexternal_id__v	Read
   sent_email__v	double_opt_in__v	n/a	parent_email__v	Read

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the permission set for the appropriate user profile.
4. Navigate to Objects.
5. Grant the following permissions:

   Object	Object Types	OLS	Field	FLS
   consent_header__v	n/a	n/a	allow_confirmation_by_email__v	Edit
   consent_type__v	n/a	n/a	double_opt_in__v	Edit
   multichannel_message__v	double_opt_in__v	Create Read Edit Delete	consent_confirm_html_file__v html_message_file__v message_identifier__v name__v object_type__v	Read
   multichannel_route__v	consent_confirmation__v	Read	n/a	n/a
   sent_email__v	double_opt_in__v	n/a	parent_email__v	Edit

6. Navigate to Admin > Configuration > Objects > Consent Header > Layouts.
7. Add the allow_confirmation_by_email__v field to the consent_header__v layouts for all object types.
8. Set up the consent confirmation email.

1. Ensure Configuring Consent Capture is complete.
2. Navigate to Admin > Users & Groups > Permission Sets.
3. Select the permission set for the appropriate user profile.
4. Navigate to Objects.
5. Grant the following permissions:

   Object	Object Types	OLS	Field	FLS
   consent_header__v	n/a	n/a	allow_confirmation_by_email__v	Read
   consent_type__v	n/a	n/a	double_opt_in__v	Read
   multichannel_consent__v	n/a	n/a	sent_email__v consent_confirm_datetime__v related_transaction_id__v	Edit
   multichannel_route__v	n/a	Read	approved_document__v country__v default__v language__v object__v record_type_name__v vexternal_id__v	Read
   sent_email__v	double_opt_in__v	n/a	parent_email__v	Edit

1. Navigate to Business Admin > Objects > Consent Headers.
2. Select the appropriate consent_header__v record.
3. Set the consent_header_status__v field to Inactive or Staged to allow edits to the record.
4. Select Edit on the consent_header__v record again.
5. Select the allow_confirmation_by_email__v check box field.
6. Set the consent_header_status__v field to Active or Staged:
   • Active — displays consent channels and lines on the Consent Capture screen and prevents further editing
   • Staged — hides the consent records from end users while allowing consent admins to review how the Consent Capture screen displays
7. Select Save.

After toggling consent for the appropriate consent channels and consent lines on the Consent Capture screen, end users select the appropriate confirmation method in the Consent Confirmation Method section on the Consent Summary screen:

• In-person – Capture signature
• Email – Send confirmation email

  On Browser, the Email option does not display when the email template linked to the multichannel_route__v record is expired.

End users then select the appropriate email address and complete the Consent Capture process.

If there is at least one opt-in consent, the confirmation email is sent to the selected email address.

The confirmation email contains all the opt-in channels and lines captured in the same transaction, as well as a link to confirm the consent changes. When the HCP selects the link, all the selected channels and lines are opted in.

End users can review and resend confirmation emails from the Consent Capture screen. See Resending Consent Confirmation Emails for more information.

Business admins can manually expire Opt In Pending consent records to allow end users to capture consent again. See Expiring Pending Consent Records as for more information.