Dropzone Contact Groups

Overview

Dropzones with a high number of recipients, who in turn have a high number of Trusted Browser Keys, can suffer from slower upload performance. This is a natural consequence of the computational intensity of asymmetric encryption, which is a time-intensive process, particularly where large files are concerned. 

Fortunately, we have a solution! If your Dropzone is suffering from performance issues, and your end users are reporting slow upload times, our Support team can convert your Dropzone recipient list to a Contact Group.

This will expedite upload times, and empower new Dropzone recipients to gain access to submissions via secure link immediately, rather than after a synchronization period.

Caveats

There are two caveats to this conversion, which you should understand before requesting it.

Package access changes  

Converting a Dropzone recipient list to a Contact Group prevents its recipients from being able to view packages uploaded to it in their History tab under Received Items. If you intend to convert your Dropzone recipient list, therefore, you should first ensure that you are using a webhook for notifications.

This way, upon Dropzone submission, you can programmatically post the fully keyed link to the submitted package into a ticketing platform such as Zendesk, Salesforce, Intercom, Freshdesk, or Jira, or into some other platform of your choosing.

Once your recipient navigates to the fully keyed link for the first time, the package will appear in their History tab. This will reduce clutter in their Received Items, and improve the agent experience for recipients on high-volume Dropzones.

Modifying the Contact Group   

The Dropzone recipient list Contact Group does not, at the time of this writing, behave like a "normal" Contact Group in SendSafely. Although it is a personal Contact Group belonging to the account that owns the Dropzone–ideally a Service Account–it does not appear in that account’s list of Contact Groups in the SendSafely web portal. It is also not currently exposed to the SendSafely API, and cannot yet be targeted by our Contact Group endpoints.

From the Dropzone owner’s, Dropzone manager’s, or SendSafely administrator’s perspective, this Contact Group is essentially operating behind the scenes. In order to modify its members, therefore, the Dropzone owner or manager, or SendSafely admin, must modify the recipient list on the Dropzone’s settings page–or, using the Dropzone owner’s API credentials–via our Dropzone recipients endpoints.

Conclusion

Once you understand the above caveats, and are ready to convert your Dropzone recipient list to a Contact Group, have a SendSafely administrator from your portal email [e-mail] with the name of the Dropzone in question, and we’ll handle the conversion for you.

You should see marked performance improvements as soon as the conversion is complete!