Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Securely Send and Receive Sensitive Data and Files Inside Salesforce

Transport sensitive data and documents in and out of Salesforce with no pins, passwords, logins, accounts, apps, or software to download with Secure File Transport. Fully compliant with multiple regulatory agencies including GDPR, SOC2, and HIPAA.

Documents Provide by Botdoc

Security Document

Workflow

  1. Salesforce User initiates a document pull request via BotDoc by sending the relevant information in the request call.

  2. BotDoc generates the request and sends the upload link via email/text to the consumer to upload the required files.

  3. The consumer does a two-factor authentication and uploads the files to BotDoc.

  4. BotDoc makes a secure connection with the Salesforce and notifies the Salesforce user that an action has been taken on the request.

  5. Salesforce pulls the document from the BotDoc repository.

  6. Optionally we can also save the document to other repositories (SharePoint, BOX.com, Google Drive, etc.

Cloud Maven, Inc doesn’t store nor transmit any 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 is salesforce can be encrypted using the salesforce shield product.

Schema Diagram - All data will be stored inside salesforce. “File Request” can be linked to any object.

Salesforce AppExchange Link

  • No labels