Use protected messages and files alongside the email and desktop tools your team already knows.
The supported add-in creates protected packages, inserts secure links and supports File Drop requests. Install through the supported sideload or administrator setup. Review the message and the protection settings before sending.
Explore this workflow →The add-on uses a connected Google and We Secure Data account. The current compose flow requires exactly one To recipient with no Cc or Bcc. Create the protected content, insert its branded secure link into the draft and send the Gmail email yourself. It also inserts File Drop requests.
Explore this workflow →Select files and choose the installed desktop secure-send action. Configure the recipient and send through the protected workflow. Supported desktop sending and Vault sync are included with Professional and Business; device and organisation policies still apply.
Explore this workflow →Business includes the Secure Sending API for approved authenticated integration. Agree the supported operations and integration requirements rather than assuming arbitrary access to every application function.
Explore this workflow →Inserting a link does not turn all surrounding ordinary email text or attachments into certified content. Create and send the content through the supported protected workflow. The recipient follows its access policy; account-free access exists, while account login can be required.
No. They use different compose and authorisation flows. Gmail currently requires one To recipient and no Cc/Bcc. Outlook setup and supported clients depend on its add-in installation. Both provide the supported protected-message and file-request workflows; follow each guide.
No. Outlook, Gmail and desktop integration are included with Professional and Business. Business alone includes Secure Sending API access.
Explore the real product workflows or register your interest in the hosted platform.
