Securely share a PDF document with anyone.
Complete guide to securely sharing a PDF document, with comments, expiry, activity tracking, terms and more. Great for meeting compliance and governance objectives.
Last updated
Complete guide to securely sharing a PDF document, with comments, expiry, activity tracking, terms and more. Great for meeting compliance and governance objectives.
Last updated
Objective
In this example we’ll be achieving the following objective with a fictional organisation named “10docs Ltd”, a large retailer.
The organisation needs to roll our a new Occupational Health and Safety policy. Its critical that everyone in the organisation receives the document, and that the organisation can demonstrate this happened for compliance reasons.
The tool needs to work with standard PDF documents, and browsers, and be available from any device.
Note: This is not a digital signature tool. Whether it complies with your organisations legal requirements can only be assessed by your own legal counsel. The document is secured using a complex URL, however, anyone with the URL can access the document.
The tool should present the document like this:
Power Automate is a growing platform, with an enormous number of first and third party connectors. Tendocs works with them all. To keep it simple, this example uses the following connectors:
SharePoint for Document storage
Tendocs for comparing the documents
Tendocs for creating the document summarising the differences
If you need any help along the way, feel free to reach out to the support team.
So you can test this yourself, exactly as described here, you can download copies of the sample documents used. Then, to get started, all you need is a SharePoint site with a Document Library where you can upload them.
Secure Document Email sample.
Note: This document was created using our Template Builder, try it yourself.
Create a new Document Library or use a Document Library in an existing site. Upload the document you would like to securely share.
Then go to the Power Automate home page.
Create a new Flow “Instant Cloud Flow”, and then complete as follows.
Add the "Get File Contents" action to retrieve the Occupational Health and Safety Policy.
Add a "Get future time" action to define when the document should expire.
Once a document expires, then it is not longer available for viewing. All documents must have an expiry time.
Add the "Securely share a PDF document" action from the Tendocs connectors.
There a number of options to configure, the below table will step you through each of them.
The following properties are available after clicking "show all" in the Tendocs action.
Configuring these options is all that is needed to create the secure document share page. The result of the action is the secure URL. This can be sent to the user via a number of channels, including Microsoft Teams, Email or messaging services. The document is only as secure as the URL, anyone with the URL will be able to access the document until the document expires.
Whenever the document is accesses an Activity record is created. This records the time, IP address and an approximate location. This is displayed on the page so the recipient can validate that only they have accessed the document. "Reporting" an issue will send a notification to the Organisation Owner.
Share the secure document web page via email by adding a "Send and email" action. The "Secure Document Email" sample in this guide is an example of a HTML formatted email. You can copy and paste this into the standard Outlook Action after toggling the "Code view" button, which is the last button on the toolbar.
The final result is an email sent to the recipient, with a URL that takes them to a page that presents the secure document as configured in the Tendocs action.
This is just a start, and you can add additional features to do things like:
Combine this functionality with Tendocs templating and Excel to automate the generation and sending of individually personalised documents in bulk.
Convert documents into PDF automatically using the Tendocs Convert action.
You can host this service on your own domain for even better security, reach out to our support team.
Option | Description |
---|---|
Option | Description |
---|---|
PDF Document
This is the File Contents of the PDF document that you would like to securely share.
Document Title
This is the "Title" that is displayed at the top of the web page presenting the document to the recipient.
Document Introduction
This is some introductory text that is included above the file. It should provide the recipient with some background and instructions.
Recipient Email
Email address of the recipient. Included so that the recipient can validate they are the correct recipient.
Recipient First Name
The first name of the recipient. This is use to validate that the recipient is correct, and also used in the "Sign" functionality.
Recipient Last Name
The last name of the recipient.
Expiry Date
The date after which the document will no longer be accessible.
Organisation
The name of the organisation who has sent the document to the recipient. This could be a company name, department, or anything else that makes it clear to the recipient who sent the document.
Organisation Email
The email address of the organisation that could be used for any questions or concerns.
Organisation Owner
The name of the person responsible for the process that has sent the document to the recipient.
Document Logo
Full URL to a logo that is then displayed to the left of the document title.
Checkbox
If you would like a checkbox that requires the recipient checks then you can include a text description of the text box here. For example "Tick this box when you have read the document". The document cannot be "Finished" until it is checked.
Sign
Requires the user to enter their full name into a text box below their full name. The document cannot be "Finished" until this is done. This is NOT a legal digital signature.
Organisation Website
A URL to a web site of the organisation. This could be internal or external, and could provide more details on the process to the recipient.
Organisation Owner Title
The job title of the person responsible for the process that has sent the document to the recipient.
Comments
Determines whether or not you would like to include the ability for the recipient to add a comment to the document.
Project ID
A unique identifier for this process. Enables you to tag related shared documents into a single process so that they can be included together in reporting.