Secure Email

Installation and Prerequisites

Cloud Maven’s Secure Email solution integrates seamlessly with Paubox to allow Salesforce users to send and receive HIPAA-compliant encrypted emails directly from within Salesforce.

This Post-Installation Guide walks administrators through the configuration steps required after installing the package.

Please ensure that you have the appropriate Salesforce administrative privileges before proceeding with the installation and configuration process.

Click here to Discover the full range of features offered by the Secure Email


2. Intended Users

  • Salesforce Admins – Responsible for setup and configuration

  • End Users – Business users who use Secure Email for exchanging secure emails.

  • Developers – Those integrating with external systems.


3. Prerequisites

3.1 System Requirements

Salesforce Professional, Enterprise, Unlimited, or Developer Edition

Required Salesforce permissions (System Admin access)

3.2 User Roles & Permissions

Admin Access – Required for installation and configuration


4. Installation

4.1 Using Salesforce App Exchange
  1. Go to Salesforce AppExchange

  2. Search for Secure Email - Salesforce’s Leading App for Encrypted Communication & Compliance

  3. Click "Get It Now" and select the Salesforce environment (Production or Sandbox)

  4. Follow the on-screen prompts to install the package

  5. Assign user permissions during the installation process

4.2 Using Direct Package Link
  1. Reach out to support@cloudmaveninc.com for the latest managed package link.

  2. Follow the on-screen prompts to install the package

  3. Assign user permissions during the installation process


5. Post Installation Steps

5.1 Assign Licenses to Intended Users

Every user who needs to access Secure Email must be assigned a license. A license determines the baseline set of features available to that user.

Steps:

  1. Click on Gear(⚙️ ) icon → Select Set up--> Quick Find Installed Packages

  2. Find Paubox Secure Email under Installed Packages.

  3. Click Manage Licenses.

  4. From here, you can:

    • Add Users → Assign licenses to new users.

    • Remove Users → Revoke licenses from users who no longer need access.

💡 Tip: Always assign licenses only to those users who will actively send/receive secure emails to avoid license wastage.


5.2 Assign Required Permission Set

Permission Sets extend user capabilities beyond their profile. For Secure Email, the CM-Secure Email Permission Set is required.

Steps:

  1. Navigate to Setup → Permission Sets.

  2. Open CM-Secure Email Permission Set.

  3. Click Manage AssignmentsAdd Assignments.

  4. Select the intended users → AssignSave.

Users now have the required permissions to access Secure Email functionality.


5.3 Remote Site Settings

  1. Click on Gear(⚙️ ) icon → Select Set up--> Quick Find Remote Site Settings

  2. Create an Entry for URL: https://api.paubox.net if it doesn’t exists.

  3. Make it Active & Save.


5.4 Enable Secure Email Feature (Protected Setting)

  • Now, Go to Custom Settings and Click on Manage of “Features Entitlement“.

  • Mark the checkbox true for Secure Email.

In case we do not have the backend access, you can run the below code snippet to enable the feature since it is protected setting.

cmsecureemail.AdminUtilityServices.enableSecureEmailFeature(true);

5.5 Update Credentials (Protected Settings)

5.5.1 Domain Activation

  • Email support@cloudmaveninc.com with your sending domain (e.g., @yourcompany.com).

  • Cloud Maven will activate your domain in Paubox.

5.5.2 DNS Verification

Update DNS records on your domain host:

  • SPF Record

    • Host: Your domain

    • Value: v=spf1 include:_spf.paubox.com -all

⚠️ Without this, Paubox will reject outbound emails.

5.5.3 Generate API Key

  1. Log into Paubox Portal.

  2. Select your domain → Click Add API Key.

  3. Save the key securely.

5.5.4 Update Credentials in Salesforce Org

After domain verification, add API credentials.

Run this in Execute Anonymous:

cmsecureemail.AdminUtilityServices.createPauBoxCredentials(<instanceName>,<apiKey>,<username>);
  • instanceName: Test or Production

  • apiKey & username: Provided by Cloud Maven

5.5.5 Enforce Paubox Portal

If you want to enforce the use of the Paubox Secure Portal for every Secure Email message, enable the Force Secure Notification setting in the Paubox Credentials configuration.

Setting:

  • Force Secure Notification (forceSecureNotification)

When this setting is enabled, all Secure Email messages are delivered through the Paubox Secure Portal, regardless of whether they would otherwise qualify for direct encrypted delivery.


5.6 Update Custom Settings

Go to Custom Settings > Data Transfer Settings and create the following entries:

  • API Connection: Test/Production

  • Possible Error Status: soft bounced,soft bounced - mailbox full,hard bounced,Internal error. Please check back later

  • Enable Dynamic Template: set to true

  • SObject Name Inbox: Field API used as parent display name in inbox.


5.7 Create a Send Secure Email Button

  1. Click on Gear(⚙️ ) icon → Select Set up--> Object Manager → Search for Source Object

  2. Navigate to Buttons, Links, and Actions.

  3. Click New Action and configure:

    • Action Type: Lightning Component

    • Component: cmsecureemail:sendSecureEmailAura

    • Height: 450px

    • Label: Send Secure Email

This makes the Secure Email component accessible from the record page.


5.8 Update Page Layouts

  1. Click on Gear(⚙️ ) icon → Select Set up--> Object Manager → Search for Source Object

  2. Go to Page Layouts. Open the Layout to update.

  3. Drag Send Secure Email into Mobile & Lightning Actions.

    image-20250925-135558.png
  4. Add Secure EmailMessages related list to track encrypted communications. Make sure to add atleast 6-8 fields while adding the related list sorting them in descending order of the CreatedDate.

    image-20250925-135858.png
  • Make sure to have the below fields:

    • From Address

    • Recipients

    • Subject

    • Email Status

    • CreatedDate (Order by DESC)


5.9 Connect Source Object with Secure EmailMessage

For objects other than Contact, Account, or Lead:

  • Check if a lookup relationship exists between Secure EmailMessage and the Source Object.

  • If not:

    1. Create a new lookup field on Secure EmailMessage.

    2. Use a Flow to auto-populate this lookup whenever an email is sent from the Source Object.


5.10 Update Custom Metadata : Email Configuration

This is required to auto populate To Address on the Send Secure Email Component

  1. Go to Setup → Custom Metadata Types → Email Configuration.

  2. Create a new Entry. Set the Label as the Object Name API

  3. Map the Source Object’s email field(s) with the Secure Email “To” field.


    58c052f1-521c-4aed-89a8-7d56a0d694c1.png

5.11 Enable Multiple To Address Mapping (Optional)

This allows users to select from multiple email fields when sending the Secure Email

  1. Navigate to Setup → Custom Settings → MultipleToAddressMapping → Click manage

  2. Click New Entry → Map additional email fields from the Source Object.

    image-20250925-150832.png

5.12 Create Lightning Email Templates

Setup Lightning Email Templates

5.13 Flow to Refresh Email Status

Create a Record-Triggered Flow on Secure EmailMessage:

  • Trigger: When record is Created or Updated.

  • Scheduled Path: 1 hour before Next Run Time.

  • Condition: Email Status = Processing.

  • Action: Call Invocable Apex cmsecureemail__InvocableUpdateEmailDeliveryStatus, passing the record Id.

This ensures email status (Delivered, Bounced, etc.) is kept up to date.


5.14 Steps to enable Secure Portal Delivery

  • Login to the Subscriber Org from the backend.

  • Go to Setup--> Custom Settings –> Paubox Credentials

  • Click Manage against the environment you want to make a change.

  • Check the checkbox forceSecureNotification

image-20260814-161936.png
  • Click Save


5.15 Flow to update the Lookup on Secure Email Message Record

Populate a Custom Lookup via Fast Field Update

5.15 Batch Job for Status Updates

BatchPullSecureEmailStatus: Batch to Get Latest Status of Secure Email



6 Inbound Functionality Setup

Click here to view more details

6.1 Create an Organisation-Wide Email Address

  1. Navigate to Setup → Organisation-Wide Addresses → Add.

  2. Verify the email.

  3. Use only the OWEA for inbound routing.

6.2 Create Email Service

  1. Navigate to Setup → Email Services → New.

  2. Enter details → Save → Create new Salesforce-generated email address.

    image-20250925-151435.png

6.3 Forwarding Rule

  • Forward all inbound messages from the Org-Wide Email Address to the Salesforce-generated email address.

📥 Now, all replies to secure emails will be captured inside Salesforce.


7. Inbox Setup

Click here to view more details

Set the Parent Display Field Name

  • Navigate to Object Manager → Secure Email Message

  • Create a new Formula (Text) field named Parent Record Name that calculates and displays the appropriate parent record's display name. This field will be used in the Secure Email Inbox to show the parent record associated with each email, providing users with a meaningful and easily identifiable record name.

  • IF( BEGINS(cm_datatransfer__Parent_Record_Id__c,'003') , cm_datatransfer__Contact__r.FirstName + ' ' + cm_datatransfer__Contact__r.LastName, Name)
    
  • Update/Create Data Transfer Settings: ParentName_SecureInbox

  • Update the value with the API Name of the Parent Record Name field.

How to initiate the Secure Email via Paubox portal

🎉 Congratulations!

You have successfully completed the Secure Email Post-Installation steps:

  • Licenses assigned

  • Permissions applied

  • Buttons and layouts configured

  • API domain verified

  • Inbound routing enabled

  • Status updates automated

Your Salesforce org is now ready for seamless, HIPAA-compliant secure communications.