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

Shared End-User Access to Dropzone Uploads

SendSafely now offers an option to automatically share access to Dropzone uploads amongst individuals within the same end-user organization.

Brian Holyfield · 2 min read
Shared End-User Access to Dropzone Uploads

SendSafely now offers an option to automatically share access to Dropzone uploads amongst individuals within the same end-user organization. This can be useful for companies that have also configured their Help Center to allow shared access to tickets within an end-user organization.

In a standard Help Center configuration, customer access to a support ticket is typically limited to the end user who originally submitted the issue. Zendesk, Salesforce Service Cloud and Freshdesk offer advanced sharing options that allow additional users within an organization to access tickets submitted by their colleagues. This ticket sharing can be accomplished by adding CC’s, configuring shared organizations for end-users, or managing user level permissions. This is useful when multiple end-users are tracking an issue, or if the original submitter is out on vacation.

zendesk_view_org_tickets

In order to take advantage of this shared ticket access, the SendSafely Dropzone can be configured to allow colleagues of the ticket submitter to access Dropzone uploads as well. This new feature, called Sender Domain Access , allows users with the same email domain as the Dropzone sender (the ticket submitter) to authenticate to SendSafely and access files posted to support tickets.

This new option can be enabled for specific Dropzones within an organization, but is turned OFF by default. A comparison of standard Dropzone authentication, and Sender Domain Access is provided below.

Standard Dropzone Authentication

Normal Dropzone uploads can only be accessed by the email address that uploaded the file (the sender) OR internal Dropzone members (recipients).

normal_dropzone_access-1

####

Sender Domain Access

With this new option enabled, a Dropzone upload can be accessed by the email address that uploaded the file (the sender), internal Dropzone members (recipients) PLUS any external end-user that has an email address within the same email domain as the sender.

sender_domain_dropzone_access

Please note the following related to this new authentication option:

Sender Domain is a premium feature available on the Enterprise plan. To enable this feature, please contact your SendSafely account representative or success@sendsafely.com.


SendSafely: Encrypted File Transfer for Modern Business

If your organization needs a secure way to transfer files with customers or business partners, our platform might be right for you. Contact us today.

Request a Demo

Frequently asked questions

Can a customer's colleagues access files they uploaded to a SendSafely Dropzone?

Yes, with Sender Domain Access enabled. Users with the same email domain as the person who uploaded the file can authenticate and access it, in addition to the uploader and internal Dropzone members. Learn about Dropzone.

Who can access a Dropzone upload by default?

With standard Dropzone authentication, an upload can only be accessed by the email address that uploaded it (the sender) or by internal Dropzone members (recipients).

Does Sender Domain Access work with Gmail or other personal email addresses?

No. Only valid business email addresses are supported. Uploads made with personal addresses such as gmail, hotmail, or yahoo are not shared through Sender Domain Access.

Is a secure link still required with Sender Domain Access?

Yes. Users also need a copy of the SendSafely secure link, and every email address is validated with a SendSafely pin code before access. With ticketing integrations, the link is typically only available to people with access to the ticket.

Why would a support team enable Sender Domain Access on a Dropzone?

It suits help centers that share tickets across an end-user organization in Zendesk, Salesforce Service Cloud, or Freshdesk, so colleagues can follow an issue or cover for an absent submitter. It is off by default and enabled per Dropzone.

Written by Brian Holyfield