Skip to content
New AI Custom Form BuilderDescribe the intake form. It ships branded and end-to-end encrypted.AI Custom Form Builder is here See it build
Integrations

Manage Package Access using Salesforce Triggers

For teams managing sensitive data in Salesforce, access control shouldn’t lag behind case activity.

Brian Holyfield · 2 min read

For teams managing sensitive data in Salesforce, access control shouldn’t lag behind case activity. SendSafely’s new case trigger functionality syncs package access with case status and assignment changes, automatically updating, revoking, or deleting access as needed.

This new feature allows customers to configure a variety of trigger actions including:

Using triggers allows you to update authorization in SendSafely in a smooth and seamless fashion, limiting access to sensitive data to the minimum number of users necessary.

This new feature is deployed as a self-hosted AWS Lambda Function, called by webhook from any Salesforce Apex Trigger. For example, you may choose to invoke this Lambda when a case is closed, when a new agent is assigned to a case, or when some other property of the case changes. The Lambda currently supports the below actions, and can also be modified to add and remove package recipients on an ad hoc basis.

This new AWS Lambda function is deployed via a CloudFormation template. For more information on set up and configuration, please see this article.

SendSafely for Salesforce is available on the SendSafely Business and Enterprise plans. For more information, contact success@sendsafely.com.

SendSafely: Integrated File Transfer for the Apps you Love

If you are looking for a secure way to send or receive files with anyone, or simply need a better way to transfer large files, our platform might be right for you.

Request a Demo

Written by Brian Holyfield

Frequently asked questions

Can SendSafely revoke file access when a Salesforce case is closed?

Yes. SendSafely case triggers can remove all recipients, including contact groups, from every SendSafely package belonging to a Salesforce case when it closes. Triggers can also update access when a case is reassigned or permanently delete packages based on case status. See the Salesforce integration.

What actions do SendSafely Salesforce case triggers support?

The Lambda supports five actions: revoke access to packages, add a user to packages, add a contact group to packages, remove a user from packages, and delete packages. Each applies to the SendSafely packages belonging to a particular Salesforce case, and the function can be modified for ad hoc changes.

How are SendSafely Salesforce case triggers deployed?

The feature is deployed as a self-hosted AWS Lambda function using a CloudFormation template. A Salesforce Apex Trigger calls the Lambda by webhook, for example when a case closes, a new agent is assigned, or another case property changes.

Why sync SendSafely package access with Salesforce case activity?

Syncing access limits sensitive data to the minimum number of users necessary. When a case is reassigned or closed, access to its SendSafely packages updates automatically instead of lagging behind case activity.

Which SendSafely plans include the Salesforce integration?

SendSafely for Salesforce is available on the Business and Enterprise plans. Setup and configuration steps for case triggers are in SendSafely’s help center article on Salesforce Case Triggers.

Keep reading

Integrations

Manage Package Access using Zendesk Triggers
Security

Your Customers' Sensitive PII Shouldn't Be Training Someone Else's AI
Customers

Keeping Unwanted PII out of your Service Desk