| Table of Contents | ||||
|---|---|---|---|---|
|
...
SF user will compose an email using a custom screen inside salesforce. The user will click on the “Send” button, which will trigger the email and an email record inside salesforce attached to the entity.
The system will invoke an HTTPS Rest API requests to PauBox to send the email. Data in-transit will be encrypted using TLS 1.3 or TLS 1.3+ protocol, and data at rest is encrypted using the AES 256 encryption.
The patient/customer will receive the encrypted email. If the patient/customer is using a browser(email client) that supports TLS 1.3 or TLS 1.3+, the customer will see the email; otherwise, they will see a hyperlink inside the email, which will take the user PauBox hosted secure page.
The patient/customer email server will send the delivery status back to the PauBox.
Salesforce will pull the delivery data(~12 seconds) using API over the HTTPS connection and email messageId in the salesforce(This Id will be used for threading the patient/customer response).
Cloud Maven, Inc doesn’t store or transmit data using our servers. We don’t have access to the client’s data in transit or rest.
Data at rest outside salesforce is encrypted using AES 256 encryption. Data in the salesforce can be encrypted using the salesforce shield product.
How Paubox Works
...
Paubox offers 4 secure message authentication options:
...
Documents Provided by PauBox
...