Secure Email – Maker-Checker Setup Checklist

Maker

Responsible for executing the setup/configuration

Checker

Responsible for reviewing and validating the setup

1.1

Assigned Secure Email Licenses to intended Users

1.2

Assigned "CM-Secure Email Permission Set" permission set to all the provided users

2.1

Enabled Secure Email from Feature Entitlements

2.2

Added Remote Site Setting for Secure Email

2.3

Added Paubox Credentials

3.1

Set up domain in Paubox Portal. Make sure it is Verified

3.2

Setup From Email Address for the same domain

3.3

Set up Reply-To Address

4.1

Create Lightning Templates as required.

Do not use the API Name of a field that does not exist on the Object.

4.2

Added Secure Email button/component on the Page Layout/Lightning Page under the App provided by the Client

4.3

Made an entry for each object(s) in the Email Configuration metadata.

Bulk First Name and Bulk Last Name should also be mapped — required for recipient validation on Bulk Send.

4.4

In case of Multiple Email fields, Multiple To Address Custom Setting has entries for the object(s)

4.5

In case of Contact as Source Object, if the client wants a lookup, the feature is enabled

5.1

Added the Secure Email button/component to the Page Layout/Lightning Page within the client-provided app

5.2

Added the Secure Email Inbox utility to the client-provided app

5.3

Added the Secure Email related list to the source object's Page Layout with the following fields: Recipient, Subject, Email Status, From Address, Delivery Status, Record Type, Created Date (sorted descending)

5.4

Verified that the Secure Email Message record displays the stage path

5.5

Ensured the Email Recipients related list is available on the Secure Email Message page layout

6.1

Scheduled the Batch to update Secure Email Status

6.2

In case Bulk or Scheduled Email is enabled, scheduled the Batch to send the Email

7.1

Click the Send Secure Email button/component from the Source Object record

The Secure Email component displays on screen

7.2

Review the auto-populated From and Reply-To addresses on the component

Both fields are pre-filled automatically with the configured From and Reply-To addresses

7.3

Review the To field where an Email Field mapping is configured

The To field auto-populates with the mapped recipient field value(s)

7.4

Open the Template selector on the component

All email templates related to the Source Object are visible and selectable

7.5

Select a template and recipient(s), then click Preview

The email preview renders with all dynamic/merge-field content replaced with valid, real values — no unresolved tokens or blank merge fields

7.6

Click Send

A Secure Email Message record is created, with one Email Recipient child record per recipient; every recipient's status is Processing

7.7

Wait for the configured interval and confirm the scheduled batch/Invocable runs

The Secure Email Message status and all related Email Recipient statuses update from Processing to Delivered

8.1

From a Object List View, select few records and click Send Bulk Secure Email

The Bulk Secure Email Visualforce page opens, listing the selected recipients count

8.2

Review the auto-populated From Email Address

Pre-filled based on org configuration

8.3

If multiple email fields are mapped on Contact, select which field to use as the destination address

Recipients re-evaluate into Eligible vs Missing Email Records lists based on the chosen field

8.4

Review the Eligible list and the Missing Email Records list

Contacts with a valid email appear under Eligible; contacts without one appear under Missing Email Records

8.5

Choose Use Template and select a Lightning Email Template for Contact

Template loads with merge fields (e.g., {!Contact.FirstName}) ready to resolve per recipient

8.6

Alternatively, choose Write Manually

Custom subject/body fields become editable and required

8.7

Attach a file under the bulk send's size limit

Attaches successfully

8.8

Attach a file over ~3 MB (the bulk LWC's client-side MAX_FILE_SIZE limit) but under the 8.5 MB single-send limit

Upload is rejected — confirms bulk enforces a smaller limit than single-send

8.9

Click Send Secure Email with a required field (From, Reply-To, email field, subject/body) left blank

"Please fill up the required fields" error displays; send is blocked

8.10

Click Send Secure Email with all required fields completed

A confirmation popup appears

8.11

Check Secure Email Message records after send

One record is created per Eligible recipient only, with Email Status = Created and Process Via Batch = true; Missing Email Records are not created

8.13

Wait for the BatchSendSecureEmail job to run

Eligible records move from Email Status = Created → Processing

8.14

Wait for the status-pull batch (BatchPullSecureEmailStatus) to run

Final status reflects Delivered (all recipients delivered), Partially Delivered (mixed), or Failed (none delivered)

8.15

Spot-check individual Secure Email Message + Email Recipient records

Merge field content is correctly personalized per recipient — no cross-record mix-ups

9.1

Make Sure ChangeSet has all the components

9.2

Before deployment, compare the code in Production with your changes to ensure that only the intended changes are being deployed. This will help prevent accidentally overwriting any existing Production code or changes made by others.

Maker Name

Date

Checker Name

Date