How to Use Secure Document Request (SDR)
Last updated
Last updated
Click on the “New Document Request” button in the top-right corner of this screen. This will allow you to choose from the existing templates to quickly create a new secure document request.
On the resulting screen you will see a list of existing templates that can be used for requests. Your organization may have lots of templates pre-configured for you to use. Choose the “Organization Templates” tab and click on the arrow on the right hand side of the template name in order to begin your request.
Fill in the following details: (* are required fields)
Document Request Details:
*Request name or ID: This allows you to set a unique name for your request. If you have a lot of requests it can be important to come up with a naming scheme so that you can easily search or scroll to find a particular request later.
Project Name: Filling in project name make it easy for you to categorize and search for historical requests. This also allows you to dictate where requested information will reside in backend storage.
Recipient Information:
*Recipient full name: This name will appear in the email sent to the recipient of the request. It’s important to set the properly to reduce confusion by the recipient of the request.
Require Fields: Leave checked any fields from the template that you want to include and clear any that are not needed in this particular request. Note that you cannot change the required status of the field (that’s done in the template configuration); if you include a required field it will be required for the user to complete the form.
Additional Options
Require one time password: This is an email verification feature that sends a code to the recipient and this code will be required prior to them opening the request.
Skip Encryption: If for any reason you do not want the information to be encrypted once received, meaning anyone can view the information this option is available.
Once you have completed the configuration of your request hit the Next button at the bottom of the page to proceed to set your encryption policies.
Encryption policies allow you to add other users or groups that can access the information once it has been submitted. Users and groups included in the encryption policy will be able to see the request in their list as well as see the status and, once completed, access the information submitted by the recipient.
Add users to the policy in the same way you would throughout the Confidencial.io interface, previous encryption policies that you have used are accessed using the left-right arrows at the top right corner of the policy interface.
Once your policy is complete you are ready to review and send the request to the recipient. Click the send request button at the bottom of the page and an email will be sent to the recipient, initiating the SDR process.
The Review fields are as follows:
Title: Shown to the recipient, this is the title of the form that the user will fill out to respond to the request. Use a short but descriptive title that describes the type of information for which you are asking.
Subtitle: Shown to the recipient. Provide additional details about the request or provide additional instructions.
Description: Not shown to the recipient. This is used internally to help users choose the correct template.
Name - Not shown to the recipient. Used internally to name the template helping for searching or scrolling when looking for the template.
isPrivate: Not shown to the recipient. This field indicates whether or not this template is shared with your organization or is only private to you.
The list of document requests to which you have access is displayed as soon as you navigate to “Document Requests” on the left hand navigation menu. On this page you have multiple options to search, sort and view requests that you have created as well as those shared with you.
Each document request has several attributes that you can view. On the left-hand list of document requests you can see the name of the request, to whom it was sent, as well as it’s age. Additionally you have a status “pill” which will show you the state of the request. The following states apply to document requests:
Not Started: The request has been sent but the recipient of the request has not yet submitted any of the related information.
Pending: The recipient has started fulfilling the request but has not yet completed all of the mandatory fields and documents.
Complete: The request has been fulfilled and the recipient has completed all of the mandatory fields and files and submitted the response. This is ready for you to view the data.
You can search for a specific request using the Search button. Search by:
Request Name
Request Uniqe ID (UUID)
Project Name
Date Range
Select the desired request.
Text viewing options:
Show Encrypted Text: If you have been added to the policy to view the data for this request the fields will change from **** to text that was uploaded.
Download all: Will download text and forms combined in a zip file
Download Text Only: Will download text in JSON.txt file
Form viewing options:
View: View in Confidencial PDF viewer
Download Encrypted: Form will be downloaded locally in encrypted form
Download Unencrypted: Form will be dowloaded locally in unencrypted form
You are able to create your own secure document templates used to create requests. You can even share them with your organization to avoid duplicate efforts and ensure consistent requests.
To Create and SDR template choose Document Request > Send New Document Request > + New Template
Fill out template name (this name is applied to the template itself and will show up in the list of templates)
Fill out Document request title (this will appear in the blue bar at the top of the request for the recipients to see as they are filling out the requests.)
Fill out Notification email subject line (this will appear as the subject of the email sent to the recipients
Document request title: Title that will appear in the list of document requests
Document request subtitle: Subtitle that will appear under the title in the list of document requests
Notification email subject line: Email subject line that will appear in the inbox of the recipient
Header image URL: Provide a custom image URL that will appear on the header of each page of the form sent the the recipient.
Background image URL: Provide a custom image URL that will appear as the background image of the form sent to the recipient.
Require one time password: This is an email verification feature that sends a separate code to the recipient which will be required prior to them opening the request.
Use template-defined access policies: This will remove the option for you to define a custom access policy for this request and use the one that was defined on the template during template creation.
You can create multiple sections for a document request. Section types include:
Custom Form: Choose when looking to request information to be filled out or uploaded in fields.
W9 Form: Choose if looking to request recipients fill out W9 form
Terms: Choose if you want to add a terms section within your request. Ex: Terms and Conditions
Success Message: Choose if you want to add a custom success message at the end of the request.
*Note Confidencial automatically shows a successful upload message and sends a success email once recipients complete the request.
The Custom Form> Section type allows you to create a section with one or multiple field types to be filled out by a recipient.
To add a Field Type such as a file upload box to your section, choose Custom Form > section type, File > field type
Add a Field Name
Select allowed file types to be uploaded by recipients
Select add field to add additional File upload boxes
Select add field
*if adding addition file upload boxes select “Make Field Optional” this will ensure they can still submit the request if only one file/folder is uploaded.
To another Field Type to this sections such as a Text area select the Textarea > field type
Add a Field Name
Select Min and Max Length if desired
Select add field
This process can be repeated with as many fields your form required.
When you have added all the appropriate fields select Add Section.
Once you have completed your template select Preview to view what is will look like when sent to the recipients.
Example Instructions Section:
Example Custom Form Section:
Once you have previewed the template and have no additional edits select Done to save the template.
The template will now appear in your template list, and you can use it by clicking the arrow on the right of the desired template in your list.
💡 File upload requests: When requesting file uploads you are able to combine them with other information requests like shown in the Client Intake Form above. you can also create templates for file request only. Confidencial can support any file types and file sizes up to terabytes.
To edit a template you must copy it from the original and then you can edit the copied version.
It is recommended you re-name your copied template.
Once you have copied the template you can edit any section of the template by clicking on the three dots > Edit.
Once you have complete the changes click on save changes.
💡 Confidential Secure Document Request process is designed to ensure that only authorized personnel can access and request classified documents, protecting against unauthorized disclosures and data breaches. This process involves on information requested using SDR. This training module will guide you through the key steps and considerations for handling confidential document requests securely and efficiently.
To securely request documents and information from anyone, login to and navigate to “Document Requests” on the left-hand navigation menu. This will show you all of your previous document requests and their current status (See ).
If you do not have existing templates or you want to create your own, please proceed to “”.
*Email address: The email address used to send the request to the recipient. Once you send the request the recipient will explaining what they are being asked to do.
For more information about encryption policies, see the documentation.