Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
ℹ️ You’ve received a Word doc that’s been secured with Confidencial…now what? This tutorial walks you through what to do. We’re going to pretend you are Bob, you’ve never used Confidencial before, and your coworker, Alice, has sent you a Confidencial Word doc.
Open the document that you received from Alice in Word
With the add-in installed, you can now click Confidencial on the right side of the Home toolbar
Once you are logged in, click View Encrypted Content in the Confidencial task pane
✅ You can now see the content that Alice protected for you.
💡For the steps Alice took to send this doc, see .
ℹ️ Since Confidencial’s keeps documents in their original file format, you can open them in their native application (Microsoft Word in this example).
Notice in the above example that you can already see some of the content. This is because Alice added a message for everyone to see after she protected the rest of the document. You can also see that there is other content that only you (bob@example.com) and Alice (alice@example.com) are authorized to see. To see this protected content, by clicking My add-ins under the Insert toolbar and then searching for “Confidencial” in the add-in store.
You are now asked to log in. When Alice sent this document to you, she also invited you to Confidencial. to create a login for Confidencial. Go to your inbox and click the link in the invitation email. From there, you will create a password and generate your encryption keys.
Now that you have a , you can by clicking Individual Log In
⚠️ If you are a member of a , you will log in using the Organization Log In button
ℹ️ Let’s say you’re George Jetson and you work at Example Company. You just finished a proposal and want to send the final product to your two subcontractors, Spacely Sprockets and Cogswell Cogs. However, there’s a problem - you can’t let them see what the other is doing in your proposal (they’re both very secretive about the work they do and the prices they charge).
In the old days, you’d have to create a separate PDF file for each subcontractor and redact the information they aren’t allowed to see. In this example, that’d mean creating three different versions of your proposal and sending a separate email for each person to get their copy. Make sure you send the right copy to the right person!
Fortunately, you don’t have to do this anymore. With Confidencial, you can do all this with a single PDF file and a single message. You don’t have multiple, unprotected copies of your proposal floating around and you don’t have to worry about getting multiple emails set up with the right attachment and sent off to the right people. Let’s see the modern way to securely share a PDF file…
Click PDF Protector
Click Open PDF File
Select your PDF file (our proposal in this example)
You can now see your proposal (PDF) in Confidencial’s PDF Protector
Select a part of the proposal that you only want Cosmo Spacely to be able to see
You and Cosmo are now in the recipients list
To encrypt the content you selected for Cosmo, click the “gear” button and choose Encrypt Selection from the menu, then click the blue Encrypt Selection button.
The selected content is now protected. Only you and Cosmo will be able to view it.
Repeat Steps 6-9 for the other parts of the proposal that you want to protect
💡 Pro tip: You can remove someone from your recipients list by clicking the X next to their name.
With all parts protected, click the download button in the toolbar to save your PDF
💡 Pro tip: When you download (save) the PDF file, you can overwrite the original version of the PDF. Doing so will replace the original, unprotected PDF with a protected, Confidencial PDF.
Now that you’ve saved your Confidencial PDF file, send it to Cosmo and Mr. Cogswell (we use Slack in this example). Remember, since access control is built directly into this PDF, you send the same version to everyone. No more sending multiple versions to multiple people with multiple messages!
✅ Your subcontractors are now ready to view the proposal.
Open the Confidencial or go to and if you haven’t done so already
in the right taskpane. You can do so by entering his email address, or, if you’ve sent to him before, click in the input box to show a list of your recent recipients.
Open the workbook that you received from Alice in Excel
With the add-in installed, you can now click Confidencial on the right side of the Home toolbar
Once you are logged in, click View Encrypted Content in the Confidencial task pane
✅ You can now see the content that Alice protected for you.
ℹ️ You’ve received an Excel workbook that’s been secured with Confidencial…now what? This tutorial walks you through what to do. We’re going to pretend you are Bob, you’ve never used Confidencial before, and your coworker, Alice, has sent you a Confidencial Excel workbook. 💡 For the steps Alice took to send this workbook, see .
ℹ️ Since Confidencial’s keeps documents in their original file format, you can open them in their native application (Microsoft Excel in this example).
Notice in the above example that you can already see some of the content. This is because Alice added a message for everyone to see after she protected the rest of the workbook. You can also see that there is other content that only you (bob@example.com) and Alice (alice@example.com) are authorized to see. To see this protected content, by clicking My add-ins under the Insert toolbar and then searching for “Confidencial” in the add-in store.
You are now asked to log in. When Alice sent this workbook to you, she also invited you to Confidencial. to create a login for Confidencial. Go to your inbox and click the link in the invitation email. From there, you will create a password and generate your encryption keys.
Now that you have a , you can by clicking Individual Log In
⚠️ If you are a member of a , you will log in using the Organization Log In button
ℹ️ You’ve received a PDF that’s been protected with Confidencial…now what? This tutorial walks you through what to do.
Let’s say you’re Cosmo Spacely, an employee at Spacely Sprockets. A collaborator of yours at another company, George Jetson at Example Company, has sent you a Confidencial PDF in Slack (but it just as easily could have been Teams, Outlook, Google Drive, or any other way you two exchange files). As you can see below, there are some parts of the document that are encrypted. Let’s walk through how to view those encrypted parts…
Click PDF Protector in the sidebar menu
Click Open PDF File and select the PDF file you downloaded from Slack (or whatever messaging app George used to give you the PDF)
You can now see the PDF with the protected parts blocked off
Click View Encrypted Content in the right taskpane
The protected parts that George has allowed you to see are now visible
✅ Congrats! You now know how to view protected PDFs with Confidencial.
💡 For the steps George took to send this PDF, see .
First, with Confidencial if you haven’t done so already. You need to do this so Confidencial can ensure that protected data is made visible to the right people. The first time someone sends a Confidencial document to you, you will receive an invitation email like that below. Simply click the button in the email to create your account.
ℹ️ If you’re part of an organization that is using Confidencial, you will probably not need to verify your email; simply to with your enterprise credentials using an
With your email verified, you can now go to and . If you verified your email address in the previous step, you’ll automatically be taken there and logged in.
💡 In addition to , you can also use the Confidencial to view protected content in Confidencial files
In the text input on the Encryption Tools page, enter the password you want to send to Bob
Enter Bob’s email address in the recipient adder
Since Bob isn’t an existing Confidencial user, invite him to join by clicking Send Invite to…
Now that you’ve invited Bob to join, click on his email in the recipient adder to add him to your protected message
Bob now appears, along with you, in the list of recipients for the message
ℹ️ The recipients list determines who can view protected content. You are automatically added as a recipient of any message or file you encrypt, so you will always be able to decrypt any message or file you protect.
Click Encrypt
This produces an encrypted message that you can now send to Bob. Click Copy to Clipboard.
You can now paste the encrypted message into your preferred messaging tool. In this example, we will use Slack.
ℹ️ Let’s say you are Alice, an employee at an organization that is using Confidencial, and you want to send a protected Word document to your coworker, Bob, who is not using Confidencial. This tutorial walks you through how to do that.
In Word, open or create the Word document that you want to protect
Since Bob is not an existing user, click Send Invite to… to invite him to Confidencial
Now that Bob has been invited, select his email to add him as a recipient of the document
You (Alice) and Bob now appear in the recipients list
ℹ️ The recipients list determines who can view protected content. You are automatically added as a recipient of any message or file you encrypt, so you will always be able to decrypt any message or file you protect.
Click Encrypt Document
The document is now protected. Save the document in Word.
Use the messaging tool of your choice (Outlook, Teams, Slack, etc.) to send the document to your coworker, Bob. In this example, we will use Slack.
ℹ️ Note that even though the document has been encrypted with Confidencial, it remains a valid .docx file (Example.docx) and can thus still be opened in Word - no special viewer is required
✅ Bob now has the Confidencial protected Word document.
Fortunately, you don’t have to do this anymore. With Confidencial, you can add a layer of protection to your image that ensures it will be “end-to-end encrypted.” That is, the whole time the image is on your machine, the whole time it’s on your recipient’s machine, and at all times in between, the image can stay protected.
Let’s see the modern way to securely share a photo…
Drag your passport photo on to the encryption box of the Encryption Tools page
💡 If Bob has never used Confidencial before, you will be asked to invite him after you enter his email address. Simply click the green invite button. Bob will be able to view your protected photo as soon as he verifies his email address with Confidencial.
You and Bob are now in the recipients list
ℹ️ The recipients list determines who can view protected content. You are automatically added as a recipient of any message or file you encrypt, so you will always be able to decrypt any message or file you protect.
Select a sensitive part of the photo by clicking and dragging a box over it
Click Encrypt Selection in the right taskpane
The selected portion is now protected. Repeat Steps 5 and 6 for each portion you’d like to protect.
Click the download (save) button to save the protected image to your disk
💡 Pro tip: When you download (save) the image, you can overwrite the original version of the image. Doing so will replace the original, unprotected image with a protected, Confidencial image.
Now that you’ve saved your Confidencial image, send it to Bob however you like. You can use email, iMessage, Slack, Teams…any method you prefer. Since access control is built directly into this image, Confidencial’s protection stays with it no matter where it goes or how it gets there.
✅ You’ve now sent your passport the safe way - the Confidencial way! If any unauthorized user intercepts your message or otherwise gets their hands on your image, below is all they will see. Only your designated encryption recipients (Bob in this example) will be able to see the protected content using Confidencial.
ℹ️ Let’s say you are Alice, an employee at an organization that is using Confidencial, and you want to send a protected Excel workbook to your coworker, Bob, who is not using Confidencial. This tutorial walks you through how to do that.
In Excel, open or create the Excel workbook that you want to protect
Since Bob is not an existing user, click Send Invite to… to invite him to Confidencial
Now that Bob has been invited, select his email to add him as a recipient of the workbook
You (Alice) and Bob now appear in the recipients list
ℹ️ The recipients list determines who can view protected content. You are automatically added as a recipient of any message or file you encrypt, so you will always be able to decrypt any message or file you protect.
Click Encrypt Workbook
The workbook is now protected. Save the workbook in Excel.
💡 By default, Confidencial encrypts the entire workbook. If you want to encrypt only certain parts of the workbook, click the “gear” menu and choose Encrypt Selection.
💡 Pro tip: Even after you’ve protected a workbook by clicking Encrypt Workbook, you can add additional content to your workbook - this content will remain visible to anyone who has access to the workbook. The protected content that you encrypted in the previous step will still only be visible to the people you designate in the recipients list.
Use the messaging tool of your choice (Outlook, Teams, Slack, etc.) to send the workbook to your coworker, Bob. In this example, we will use Slack.
ℹ️ Note that even though the workbook has been encrypted with Confidencial, it remains a valid .xlsx file (Example.xlsx) and can thus still be opened in Excel - no special viewer is required
✅ Bob now has the Confidencial protected Excel workbook.
ℹ️ You’ve received an image that’s been protected with Confidencial…now what? This tutorial walks you through what to do. We’re going to pretend you are Bob who works at The Example Hotel, you’ve never used Confidencial before, and one of your international guests, Happy Traveler, has sent you a photo of her passport.
If you open the image that you received from Happy in your default image viewer, you will see an image like that above. You will be able to see all the parts of the image that Happy chose not to protect. To see the protected parts, continue to the steps below.
Once you are logged in, drag the protected Confidencial image file on to the encryption box of the Encryption Tools page
The protected image is now displayed in the Confidencial Image Protector
Click View Encrypted Content in the right taskpane
✅ You can now see the content that Happy protected for you.
💡 Confidencial takes an end-to-end approach to securing your messages and files. What does this mean? In short, it means that in most* cases, Confidencial does not see or store the private keys that are required to decrypt messages and files and in all cases we do not ever see (let alone store) your messages and files, even in their encrypted form. Read on for more information about our approach to keeping your data safe.
Confidencial’s implementation is a true end-to-end secure solution to protecting your most sensitive data. This approach is perhaps best described by example; let’s review a couple of these.
When you click Encrypt Document, here is what happens:
Confidencial takes all the content in your document and encrypts it using your public key*
*️⃣ Technically, we encrypt the content of your document with a symmetric (AES) key. That symmetric key is then encrypted using your public key.
The encrypted data is then inserted into your document as metadata
ℹ️ Metadata is auxiliary information - it’s data about your data. Other examples of metadata in a Word document include the document author’s name, the title of the document, and the name of the template upon which the document is based.
When you save the document, its contents are now protected at rest
Confidencial retrieves your private decryption key
The encrypted document data is extracted from the metadata of the document
Your private key is used to decrypt the data
The decrypted data is re-inserted into your document for viewing and editing
When you are done viewing and editing the document, clicking Re-encrypt Before Saving protects the data by executing the steps described in the “Encrypting the document” section above
🔒 At no point during this entire encrypt-decrypt process did your document’s contents get sent to Confidencial. All encryption and decryption is done locally on your machine. It is an end-to-end secure process.
💬 With the release of Confidencial 2.2, you will be able to send messages and files directly from the Confidencial web or desktop app using Slack, Outlook, or Gmail! Check back here after the release of V2.2 for a description of how Confidencial implements an end-to-end solution for data sharing using your favorite messaging apps.
ℹ️ Let’s say you are Alice, a Confidencial user that wants to send a password to your coworker, Bob, who is not a Confidencial user. This tutorial walks you through how to do this. 💡 See for a tutorial on what Bob does once he receives the message
Go to and if you haven’t done so already
✅ The secure message has now been sent to Bob. Bob views the message by and .
⚠️ This tutorial assumes you already have a and have .
and if you haven’t done so already
for whom you want to protect the document by clicking in the recipient adder and entering in an email address. In this example, we are encrypting for bob@example.com.
💡 By default, Confidencial encrypts the entire document. If you want to encrypt only certain parts of the document, see . 💡 Pro tip: Even after you’ve protected a document by clicking Encrypt Document, you can add additional content to your document - this content will remain visible to anyone who has access to the document. The protected content that you encrypted in the previous step will still only be visible to the people you designate in the recipients list.
ℹ️ Let’s say you’re Happy Traveler, a tourist preparing to make a trip overseas. At your destination hotel, The Example Hotel, Bob at the front desk has asked for a photo of your passport. You understand the , and don’t want to subject yourself to possible identity theft.
Open the Confidencial or go to and if you haven’t done so already
The photo will open in the Confidencial Image Protector. in the right taskpane. You can do so by entering his email address, or, if you’ve sent to him before, click in the input box to show a list of your recent recipients.
ℹ️ The Confidencial Image Protector currently supports PNG and JPEG images. Other image types can be encrypted using Confidencial’s “C11” file format (). support for other image types is coming soon.
⚠️ This tutorial assumes you already have a and have .
and if you haven’t done so already
for whom you want to protect the workbook by clicking in the recipient adder and entering in an email address. In this example, we are encrypting for bob@example.com.
💡 For the steps Happy took to send this image, see
ℹ️ Since Confidencial’s keeps documents in their original file format, they can be opened with your default application (Microsoft Photos in the example above).
Since we’re assuming in this example that you’ve never used Confidencial before and that your guest has sent you an invite to Confidencial, the next step is to to create a login. Go to your inbox and click the link in the invitation email. From there, you will create a password and generate your encryption keys.
💡 If you already have a Confidencial account, you can skip this step. If you don’t have a Confidencial account and haven’t been invited, you can .
Now that you have a , you can by or by going to and clicking Individual Log In
⚠️ If you are a member of a , you will log in using the Organization Log In button 💡 If you just registered your Confidencial account in Step 2 above, you will probably be able to skip this step, as you will already be logged in
*️⃣ In most cases, Confidencial does not store your private decryption keys in a form that would enable an attacker to access your protected documents should Confidencial’s backend infrastructure be compromised. Besides the fact that Confidencial does not see or store your messages and documents, Confidencial does not store whole private keys in its infrastructure (with the exception of ). Instead, keys are either , , or .
Let’s say you have a Word document that you would like to protect. You might store this Word doc on your PC, on your company’s internal network, or in the cloud. Wherever you store it, Confidencial’s protection will follow it, because . If this is a working document that you are creating on your own, you will probably just encrypt it for yourself. You can to .
Confidencial fetches your public encryption key from its (or the local cache of public keys on your machine)
Your original document data is now replaced with a banner that informs viewers of the document that it is protected with Confidencial. A hyperlink is included within the banner that directs users to .
When you later open this document and , here is what happens:
🔑 Depending on , this will be done by either requesting it from , assembling it from , or by asking you to load it from your chosen
Along with the protected message from Alice, you will also receive an invitation email to join Confidencial. Click on the button in that email to create your Confidencial account.
After you click the registration link, enter a password and click Continue to create a dedicated Confidencial account or click Continue with Google or Continue with Microsoft to create an account based on an existing Google or Microsoft account, respectively
If prompted, provide consent to Confidencial to access certain information from your Google or Microsoft account. Confidencial requires information such as your email address and name to allow other users to find you and encrypt information for you.
Since this is your first time logging in, click Generate Keys. Confidencial creates your public and private encryption keys at this time. On subsequent logins, the keys you generated will be loaded automatically.
You are now taken to Confidencial’s web app, where you are able to protect and view messages
Copy the Confidencial protected message you received from your messaging tool onto your clipboard. In this example, we use Slack.
Go back to your web browser and paste the protected message into the input box on the Encryption Tools page
⚠️ Be sure to include the “BEGIN CONFIDENCIAL ENCRYPTED MESSAGE” and “END CONFIDENCIAL ENCRYPTED MESSAGE” parts of the protected message when pasting into the input box.
Click Decrypt
You can now view the protected message and copy it into other programs
✅ This is how you view protected messages with Confidencial.
ℹ️ See the links below for instructions on how to deploy the Confidencial Private Key Server
Confidencial’s in-doc encryption allows you to encrypt all or parts of documents in their native format. For example, if you , the file remains a valid “DOCX” file.
In-doc encryption means that you can view files protected with Confidencial in their native applications. This also means that anyone can view the unprotected portions of your Confidencial documents without any special viewers or add-ins. The Confidencial app or are only needed to .
Confidencial currently supports in-doc encryption for Microsoft Word, Microsoft Excel, PDF files, and PNG and JPG images. Support for Microsoft PowerPoint, and other image formats is coming soon. Have another format you’d like us support? Let us know at .
Any file type that isn’t supported by Confidencial’s in-doc encryption with the Confidencial or . In these cases, the protected file is converted into a “C11” file that can be decrypted with the Confidencial desktop or web app.
ℹ️ So you’ve received a message protected with Confidencial…now what? This tutorial walks you through how to view the message. Let’s pretend your coworker, Alice, has sent a message (a password) to you, Bob, who has never used Confidencial before. 💡 See for a tutorial on the steps Alice took to send you this message
🔑 Since this message from Alice was protected before you created an account and generated , this message was protected with a . All messages protected for you from this point forward are protected with the more secure split keys.
This documentation is coming soon
An organization account is for users within a company that has a . Organization accounts are subject to the that are set by . For example, an organization may choose to a , which allows administrators to recover (decrypt) any content that is protected by or for members within an organization.
Members of an organization can for other members within their organization, users with , and members of other organizations that have enabled.
Individual accounts are Confidencial accounts intended for individuals and small teams that do not have a . Users with an individual account can for any other user with an individual account as well as users with that .
Anyone - both individual and organization users - can
This documentation will be coming soon
Confidencial supports several types of files natively. That is, Confidencial encrypts content within these types of files while preserving the native format of the file. These file types include Word docs (.docx), Excel workbooks (.xlsx), and portable document format files (.pdf).
Just like for PDF files, Confidencial also supports native (format-preserving) protection of JPEG and PNG images in its desktop and web apps. Confidencial users can load an image in Image Protector to protect all or parts of an image. Again, like PDF files, protected images remain in their native format, so they can continue to be viewed in standard (default) images viewers with unprotected parts continuing to be visible. However, one must use the Confidencial desktop or web app (and be authorized) to view protected portions of images.
All files types that aren’t natively supported by Confidencial’s apps and add-ins can nonetheless still be protected by encrypting them with Confidencial’s .c11 file format. Like natively-supported file types, users encrypt other file types for a specific set of recipients. Users may protect either a single file or a bundle of files in this manner. Encryption and decryption can be performed in either the desktop or web app.
An organization administrator is the top-level user (has full permissions) within a . Administrators have the ability to , set that determine how members can use Confidencial, and through the use of . Administrators are also able to that takes place within an organization through the analytics dashboard.
ℹ️ See for other features available to organization administrators
Confidencial supports multiple types of files. Files are protected either (using add-ins or the Confidencial desktop and web app) or through Confidencial’s “.c11” format.
When protected with Confidencial’s , files encrypted in Word and Excel maintain their original format, meaning that the files remain valid Word (Excel) files and can be opened in Word (Excel), regardless of whether the Confidencial add-in is installed or not. However, only authenticated users with the Confidencial add-in installed can see content that is encrypted for them.
ℹ️ See , , and for more information
Confidencial supports native (format-preserving) protection of PDF files through its and apps using the PDF Protector. Users are able to and protect the entire document or parts of the document for a . Since Confidencial-protected PDF documents are valid PDF files, they can be opened in any PDF viewer. However, only authenticated users with the Confidencial desktop or web app can view (decrypt) protected parts of a Confidencial-protected PDF file.
ℹ️ See and for more information
ℹ️ See and for more information
ℹ️ See and for more information
⚠️ It is strongly recommended to NOT store device-stored keys on a device that also contains Confidencial-protected messages and files. If keys and the data protected with those keys are stored on the same device, an attacker who gains access to that device would theoretically be able to view your protected data. Instead, it is recommended that device-stored keys be stored on a device, [such as an HSM](https://en.wikipedia.org/wiki/Hardware_security_module), that is dedicated to storing cryptographic keys.
Device-stored keys are private keys that are stored on a Confidencial user’s device. This is in contrast to , which are split (sharded) and stored in multiple cloud locations. Users with and that permit it may , such as the disk of their laptop or desktop PC, a smartphone, or a hardware security module (HSM). For both device- and cloud-stored private keys, the corresponding public key is stored in .
Since device-stored keys are not stored in the cloud, whenever they are required to decrypt a given message or file.
If you are logging in with an organization account, enter your organization name and click Continue. If you are logging in with an individual account, proceed to Step 3.
Enter your email address and password and click Continue or log in with your existing Microsoft or Google account by clicking Continue with Microsoft or Continue with Google, respectively
✅ This completes the login process. You are now ready to protect your content using Confidencial.
Start by opening the Confidencial or by going to
Depending on your , click either Individual Log In or Organization Log In
are for individuals and small teams that do not have a Confidencial organization
are for users within companies that are set up with a Confidencial organization
What this means is that an attacker would have to compromise Confidencial’s backend infrastructure AND a third-party’s backend infrastructure AND they would have to compromise your chosen document store - whether that be the cloud, your organization’s internal network, or your computer - to gain access to your Confidencial-protected data.
Recovery keys allow to recover data that is encrypted for users within their organization in the event that the original recipient loses (or refuses to provide) access to their keys. Recovery keys are and are stored by the organization. Confidencial at no time has access to recovery keys, so it is important to store these keys in a reliable, secure place.
Cloud-stored keys are public-private key pairs used by Confidencial . The public key of the pair is stored in the The private key is split into multiple parts, called “shards,” with each shard being stored in a different physical (and virtual) location. This is done to increase the security of the private keys - if any one private key shard storage location is compromised, it poses no security threat to content protected with those keys, as multiple shards of a private key are required to decrypt content.
Individual account users can also opt to store their private key themselves if they wish to not use a cloud-stored key. See .
Temporary keys are public-private key pairs that are used by Confidencial to support the immediate encryption of content for newly-invited users. Temporary keys are so called because they are replaced by a (in the case of an )* or (in the case of an ) as soon as the invited user registers their account. Temporary keys are stored in Confidencial’s private key server.
⚠️ Since Confidencial stores temporary keys, content encrypted for users that are using temporary keys (i.e. newly-invited users who have not yet , while still secure, is technically not . It is recommended to designated for newly-invited users once they have registered their account.
An Encryption Policy is a set of Confidencial users that have permission to view content within a Confidencial-protected document. Every policy you create (every different set of people you encrypt for) is automatically saved by Confidencial and can be accessed later using the left arrow and right arrow browse buttons located above the Add person to policy input box. This allows you to encrypt for commonly-used groups of people without manually adding each member of the group to the policy one-by-one.
ℹ️ These instructions cover how to choose who can see the content in your messages and files
ℹ️ Note that when you protect content you are automatically added as a recipient, so you will always be able to see content that you protect for others
Choose who you want to see your content
If you want to encrypt for a new set of people, click in the Add person to policy input box. There you will see the people for which you have most recently encrypted. You can also type in a user’s email address if you have not encrypted for them before.
If you want to remove a user from your recipient list, click the X next to the user’s name
Once the desired recipients are selected, click Encrypt to protect the content
If you have used Confidencial before, you can browse through your recent recipient groups (aka your recent ) using the left arrow and right arrow buttons. These groups (policies) are automatically created every time you encrypt for a new set of people.
ℹ️ Pro tip: If you want to encrypt for someone who’s never used Confidencial, simply enter their email address. You will be prompted to .
If you are logged in to an that has , you will see a list of available encryption recipients in your organization. Click on a listing to add an encryption recipient. To chose someone outside your organization, enter their email address.
If you are logged into an organization with directory listing disabled, enter a recipient’s email address and click on the appropriate listing. If no match is found, you will be able to .
If you are logging in with an organization account, enter your organization name and click Continue. If you are logging in with an individual account, proceed to Step 3.
Enter your email address and password and click Continue or log in with your existing Microsoft or Google account by clicking Continue with Microsoft or Continue with Google, respectively
✅ This completes the login process. You are now ready to protect your content using Confidencial.
Depending on your , click either Individual Log In or Organization Log In
are for individuals and small teams that do not have a Confidencial organization
are for users within companies that are set up with a Confidencial organization
See “Accepting an invitation to create a Confidencial individual account” in
Enterprise keys are public-private key pairs in which the private key is split (”sharded”) between a that is hosted in an enterprise’s infrastructure and Confidencial’s cloud infrastructure. Using a CKS and enterprise keys offers , which means that the enterprise’s data is not compromised even if either the enterprise’s CKS or Confidencial’s servers are compromised - it would require the compromise of both infrastructures and the obtainment of encrypted documents for the data to be put at risk. When a CKS is used, Confidencial does not store any wholly-assembled private keys belonging to the enterprise. The public keys associated with these private keys are stored in , but these keys, by their nature, are intended to be widely distributed and their exposure poses no security risk.
⚠️ Content encrypted exclusively for members of an organization with a CKS is protected in an end-to-end secure manner. However, content that includes recipients with a Confidencial , while still secure, is not protected in the same way, as Confidencial individual accounts use or .
A Confidencial organization is a space within the Confidencial platform that is controlled by the appointees (usually IT administrators) of a commercial or government entity. A Confidencial organization consists of a collection of members, usually the employees of a company, that log in to the organization with . have the ability to , set that determine how members can use Confidencial, and through the use of . Confidencial organizations also , enabling single sign-on using existing accounts on IDPs such as Microsoft Active Directory and Okta.
ℹ️ See for other features enabled by Confidencial organizations
There are two ways to invite users to join Confidencial with an individual account:
Click Invite People to Confidencial
Enter the email addresses of the people you want to invite (up to 5 at a time) and click Send Invites
✅ The users you invited will now receive invitation emails. You may now encrypt content for them.
From the Encryption page of the web or desktop app, or the task pane of an Office add-in, enter the email address or the person you want to invite in the recipient box
Click Send Invite to…
✅ The user you invited will now receive an invitation email. You may now encrypt content for them.
💡 You can track the status of all your invites by clicking Invite in the web or desktop app. You can resend invite emails to users by clicking Send Again. When a user accepts your invitation, their status will change from pending to accepted.
ℹ️ These instructions show you how to invite others to use Confidencial with an . If you are part of a Confidencial and want to , contact your
⚠️ When you invite another user to join Confidencial with an individual account, a is generated for their account so you can immediately encrypt content for them. This temporary key is stored in Confidencial’s secure key server. Once the invited user registers their account, they will generate a more secure . All subsequent encryptions for them will use the split key.
Once you have sent invites, you can .
Once to the web or desktop app, click Invite in the sidebar menu
In the Encryption Tools page, enter or paste a text message into the encryption input box
Click Encrypt
Copy the protected (encrypted) message to your clipboard by clicking Copy to Clipboard
✅ You have now generated a protected message. You can paste this protected message in an app of your choosing to send to your recipient(s).
⚠️ The Confidencial app does not send messages to your recipients directly. You must do so using a third-party app of your choosing, such as Slack, Outlook, or Teams. Confidencial will support direct sending of messages from its apps via these platforms in a future release.
Go to and if necessary
for which you want to encrypt the message
From the Encryption Tools page, choose the files and/or folders you want to protect. There are two ways to do this.
You can choose files and folders by clicking the choose files link in the input box
You can drag and drop files and/or folders onto the input box
Click Encrypt
Click Save File to choose a location to store your Confidencial-protected file
✅ You have now created a Confidencial-protected file that contains the files and/or folders you selected.
ℹ️ These instructions show you how to encrypt files and folders using the Confidencial web app. You can also .
Begin by going to and if necessary
After you have selected the files and/or folders you want to protect, that you want to be able to see the protected content
ℹ️ If you selected a single file to protect, a single .c11 file will be generated that is a protected version of the file. If you selected multiple files and/or one or more folders to protect, a file bundle will be created in the form of a .zip file that contains multiple .c11 files. In both cases (single .c11 file or .zip file containing multiple .c11 files), you will be able to decrypt the file or bundle in either the or the .
ℹ️ These instructions show you how to decrypt a message you’ve received from another Confidencial user with the Confidencial web app. You can also decrypt messages with the Confidencial desktop app using a similar process.
Copy the encrypted message you’ve received in to your clipboard
💡 To copy to your clipboard
Menu (macOS or Windows): Edit → Copy
macOS: ⌘ + C
Windows: CTRL + C
Paste the encrypted message from your clipboard to the input box on the Encryption Tools page and click Decrypt
⚠️ Be sure to paste the entire encrypted message, including the parts that say “BEGIN CONFIDENCIAL ENCRYPTED MESSAGE” and “END CONFIDENCIAL ENCRYPTED MESSAGE” 💡 To paste from your clipboard
Menu (macOS or Windows): Edit → Paste
macOS: ⌘ + V
Windows: CTRL + V
✅ Your decrypted message will appear along with options to save the message to a file or copy the message to your clipboard
Drag and drop the Confidencial protected file into the encryption box or click choose files and select the file in the Encryption Tools page
Click Decrypt
If the protected (encrypted) file is a .c11 file, you can save an unprotected (decrypted) version of the file by clicking Save File. If the protected file is a .c11.zip file (a file bundle), clicking Save File will allow you to save a zip file containing unprotected versions of each file within the bundle.
✅ The completes decryption of Confidencial-protected files. These unprotected files are now available to be opened in their native viewers/editors.
Go to in your web browser and if necessary
ℹ️ These instructions show you how to decrypt a Confidencial-protected file. Individual files that are protected with Confidencial’s desktop or web app (and are not ) typically ends with a “.c11” file extension, while a file bundle (that contains multiple Confidencial-protected files) typically ends with a “.c11.zip” extension.
Start by going to and .
⚠️ Following use (viewing and/or editing), it is strongly recommended to and permanently remove (delete + empty trash) the unprotected versions from your disk
ℹ️ These instructions show you how to change the contents of a Confidencial-protected (.c11) file (and who can see those contents). The process amounts to decrypting the file(s) or folder(s), making any desired changes to the decrypted content, and encrypting the decrypted content for a new group of recipients. In an upcoming version of Confidencial, you will be able to change who can see the contents of a Confidencial-protected file without decrypting and re-encrypting.
ℹ️ Viewership: Who can see the contents of a Confidencial-protected file or folder
Make any desired changes to the unencrypted contents of the .c11 file
✅ This completes editing the content of a protected file and re-encrypting the protected file for a new group of recipients
Decrypt the .c11 file for which you want to change the content or viewership in either the or
Encrypt the just-decrypted file(s) or folder(s) in either the or , selecting the new group of recipients that you want to be able to see the contents
⚠️ After you have completed this process, it is strongly recommended that you permanently remove (delete + empty trash) the decrypted files that were produced in
There are two primary ways to create an individual account with Confidencial. You can register an account by accepting an invitation from another Confidencial user or you can create an account without an invitation.
If you have received an invitation to join Confidencial with an individual account, you will receive an email with a link to start the registration process. Click Click here to get started to start account registration.
After you click the registration link, enter a password and click Continue to create a dedicated Confidencial account or click Continue with Google or Continue with Microsoft to create an account based on an existing Google or Microsoft account, respectively
If prompted, provide consent to Confidencial to access certain information from your Google or Microsoft account. Confidencial requires information such as your email address and name to allow other users to find you and encrypt information for you.
Go to my.confidencial.io
Click Sign Up
Enter your email address and create a password and click Continue to create a dedicated Confidencial account or click Continue with Google or Continue with Microsoft to create an account based on an existing Google or Microsoft account, respectively
Depending on how you chose to create an account, you may be asked to verify your email. If you are asked to verify your email, you will receive a verification email. Follow the instructions in that email to continue creating your account.
ℹ️ These instructions show you how to create an with Confidencial. Individual accounts should be used by individuals for personal use and small teams that do not have a . Employees at companies with Confidencial organizations should use . Organization accounts are typically created and administered by an IT administrator within the company.
✅ This completes creation of a new individual account with Confidencial. You will now be taken to . If creating an account using Google or Microsoft, you may first be required to .
➡️ After your first login, you will be asked to to be used for encryption
✅ Once your email address has been verified, you will be able to to
➡️ After your first login, you will be asked to to be used for encryption
ℹ️ These instructions assume you have already
⚠️ If the Confidencial button is disabled, make sure you have an email message selected such that the message is displayed in the message preview pane. If an email is displayed in the message preview pane and the Confidencial is still disabled, then you are not using an email service that is compatible with Microsoft Office add-ins. See for information about support email account types.
In either Word or Excel, navigate to the Insert ribbon (toolbar)
(If visible) click Add-ins
Click My Add-ins
In the Office Add-ins pop-up window, click STORE
Search for confidencial
Click the Add button next to Confidencial for Word and Excel, then click Continue to accept the license terms and privacy policy
You can now launch the Confidencial add-in from the Home ribbon (toolbar)
✅ This completes installation of the Confidencial add-in for Word and Excel
⚠️ Microsoft Outlook does not support the use of add-ins with certain email server and client platforms. On Windows, you must have an Exchanged-based email account to use add-ins. On macOS, you must have an Exchange- or Google-based email account to use add-ins.
(If visible) click “…” in the toolbar
Click Get Add-ins
⚠️ If you are using a supported server and client, you will be able to see a Get Add-ins button on your Outlook toolbar. If the button is not visible or is disabled, select an email message from an eligible email account to display it in the message preview window. If the Get Add-ins button is still not visible or is disabled, then you are likely not using an email account that is compatible with Outlook add-ins.
Search for confidencial
Click the Add button next to Confidencial for Outlook, then (if presented) click Continue to accept the license terms and privacy policy
✅ This completes installation of the Confidencial add-in for Outlook
ℹ️ These instructions cover how to install Confidencial for Word and Excel and Confidencial for Outlook from the Microsoft Office add-in store (AppSource). If you are part of a company with a , you may be required to have your administrator install the add-ins for you.
Click Install on the sidebar menu
Click on the appropriate download button, based on your operating system
✅ This completes installation of the Confidencial desktop app. You can now open the app by double-clicking its icon or by double-clicking a .c11 file.
⚠️ If you are using Confidencial at work, you will likely need to have add-ins installed by your organization’s IT administrator
⚠️ These instructions cover how to install the . While installing this app is strongly recommended, you can obtain most functionality via .
Go to and
Follow the instructions presented by the installer. After installation is complete, a page will appear with instructions for .
➡️ If you use Microsoft Office, we strongly recommend following installation of the desktop app
ℹ️ These instructions cover how to log in to Confidencial add-ins for Microsoft Office. While the examples below show Microsoft Word, the process is the same for all Microsoft Office apps.
Start by clicking Confidencial in the main toolbar
If you are logging in with an organization account, enter your organization name and click Continue. If you are logging in with an individual account, proceed to Step 3.
Enter your email address and password and click Continue or log in with your existing Microsoft or Google account by clicking Continue with Microsoft or Continue with Google, respectively
✅ This completes the login process. You are now ready to protect your content using Confidencial.
ℹ️ If you have not yet installed Confidencial add-ins for Office, see .
Depending on your , click either Individual Log In or Organization Log In
are for individuals and small teams that do not have a Confidencial organization
are for users within companies that are set up with a Confidencial organization
Start by double-clicking the .c11 file; this will open the Confidencial desktop app
Drag and drop the Confidencial protected file into the encryption box or click choose files and select the file in the Encryption Tools page
Click Decrypt
If the protected (encrypted) file is a .c11 file, you can save an unprotected (decrypted) version of the file by clicking Save File. If the protected file is a .c11.zip file (a file bundle), clicking Save File will allow you to save a zip file containing unprotected versions of each file within the bundle.
✅ The completes decryption of Confidencial-protected files. These unprotected files are now available to be opened in their native viewers/editors.
ℹ️ These instructions assume you have . You can also .
ℹ️ These instructions show you how to decrypt a Confidencial-protected file. Individual files that are protected with Confidencial’s desktop or web app (and are not ) typically ends with a “.c11” file extension, while a file bundle (that contains multiple Confidencial-protected files) typically ends with a “.c11.zip” extension.
⚠️ Following use (viewing and/or editing), it is strongly recommended to and permanently remove (delete + empty trash) the unprotected versions from your disk
Click Encrypt Selection under the Settings menu (gear icon) of the Confidencial task pane
Select content in your Word document that you want to protect
ℹ️ Note that you are automatically added as a recipient, so you will always be to view any content that you protect
Click Encrypt Selection
✅ The selected content is now protected for your chosen recipients. Repeat Steps 3 - 5 to protect other parts of your document.
ℹ️ These instructions cover how to encrypt parts of a document in Word. This means that different recipients will be able to decrypt the different parts of the document. If you want to allow all recipients to decrypt the entire contents of a document, see .
Create or open a Word document that you want to protect, , and if you have not already done so
for whom you want to protect the selected content
Click Re-encrypt Before Saving in the Confidencial task pane
Save the document
✅ This will protect all content in the document for the original group of recipients
ℹ️ If the document was in the protected state (encrypted content not visible) during the last time you saved the document, you can also close the document without saving. This will leave the document in the protected state with the original recipients intact. However, it is best practice to click Re-encrypt Before Saving and re-save the document to guarantee that the document is saved in the protected state.
⚠️ If you save and share the document before clicking Re-encrypt Before Saving, all decrypted contents in the document will be visible to anyone who gains access to and opens the document.
Remove encryption from the content for which you want to change the recipients
With Confidencial protection removed from the necessary parts of the document, you can now re-encrypt the content for a new group of recipients
✅ This will re-encrypt the entire document for the new group of recipients and put the document in the protected state. The document can now be safely distributed.
✅ This will re-encrypt the parts for the new group of recipients and put the document in the protected state. The document can now be safely distributed.
Click Key Management under the Advanced section of the left sidebar menu
Information about your current encryption key is displayed. By default, your private encryption key is a cloud-stored key, which means it is split (sharded), with the parts stored across multiple, isolated cloud locations. To switch to a device-stored key - a key you store on a device of your choosing - click Replace Current Encryption Key.
Select Local File Storage then click Replace Current Key
Your new private encryption key is downloaded to your device (as indicated by the green highlight box in the lower left of the screen below)
Click the menu next to the downloaded key file to save it in a reliable, secure location. Most browsers will store files in your Downloads folder, so you will need to open that folder and transfer the key file (the name will be something like c11_key_165bd1c523605d77.key
) to a safe location/device.
Click Encrypt Document
✅ Your document is protected. You may now save it and safely send it to others.
💡Confidencial deploys Microsoft Office Web add-ins. These are built using web technologies (HTML, JavaScript, and CSS) and leverage the Office JavaScript API to interact with Office applications like Word, Excel, Outlook, and PowerPoint.
Confidencial offers central management of the add-ins for enterprise deployments where admins elect to push the add-ins to end devices.
Navigate to Settings > Integrated apps
Select "Add-ins"
Click "Deploy add-in" and then "Next"
Choose "Choose from the store"
Search for "Confidencial" in the search bar
Select "Add" for the desired add-ins (Word, Excel, and/or Outlook)
Assign users as needed and click "Deploy"
Test the deployment using the available options
Your add-ins are now successfully deployed.
For installation via Windows or macOS installer, please contact your Confidencial team for detailed instructions and support.
Note: After deployment, users can access the enabled add-ins under "My Add-ins" in their Microsoft Office applications.
Open the Confidencial-protected Word document in Word
Click View Encrypted Content in the Confidencial task pane
✅ You can now see the content that was encrypted for you and make changes to it
⚠️ If you want to re-save your document - for example, if you made changes and want to save them - be sure to first click Re-encrypt Before Saving before you save. If you save your document without re-encrypting, your content will not be protected.
ℹ️ After you have opened a and , you can re-encrypt the content. These instructions cover how to re-encrypt for the original recipients and how to re-encrypt for a different group of recipients.
if it is not open already and if necessary
if it is not open already and if necessary
If the document is using , click Remove All Encryption in the Confidencial task pane
If the document is using (only parts of the document are encrypted), for each part that you want to encrypt for a different group of recipients, select the part, then click Remove Selected Encryption in the Confidencial task pane
If you are using whole-document encryption, in the Confidencial task pane and click Encrypt Document
If you are encrypting only parts of the document, one-at-a-time select each part of the document you want to encrypt, in the Confidencial task pane, and click Encrypt Selection
ℹ️ This guide shows you how to switch to a to store your private decryption key on a device of your choosing. Advanced users may opt for this approach over using a to meet advanced security requirements or to facilitate the offline viewing of protected content.
⚠️ It is strongly recommended to NOT store device-stored keys on a device that also contains Confidencial-protected messages and files. If keys and the data protected with those keys are stored on the same device, an attacker who gains access to that device would theoretically be able to view your protected data. Instead, it is recommended that device-stored keys be stored on a device, , that is dedicated to storing cryptographic keys.
Open the or go to and if you haven’t done so already
⚠️ Since device-stored keys are generated on your device, this is the only time you will be able to retrieve the key through the Confidencial app. If you fail to save the key during this step, or later lose the key, you will need to generate a new key by repeating the steps above. All documents encrypted with the lost key will not be decryptable unless you are part of an that uses .
✅ This completes how to store keys on your device. All messages and files encrypted for you will now use this key. You will have to whenever you want to decrypt a message or document.
ℹ️ These instructions cover how to encrypt an entire document in Word. This means that all chosen recipients will be able to decrypt the entire contents of the document. If you want to control who can see each part of a document separately, see .
Once , for whom you want to encrypt
Log in to the Microsoft 365 admin center at
ℹ️ These instructions cover how to decrypt a Word document and assume that you’ve already
If you haven’t done so already, and
Click Machine Tokens under the Advanced section of the left sidebar menu
Click New Machine Token
Give your token a name and optionally a description and click Create Token
Your machine token will now be displayed
⚠️ Your machine tokens allow anyone with access to them to perform Confidencial actions on your behalf. Be sure to store these tokens securely!
🗑️ If you need to revoke a machine token, you can do so by clicking the corresponding delete link on the Machine Tokens page
ℹ️ This page describes how to create machine tokens, which allow you to execute Confidencial actions using the .
Open the Confidencial or go to and if you haven’t done so already
Click Key Management under the Advanced section of the left sidebar menu
Your keys are listed in the main panel. For each key pair that you wish to use with the SDK:
Copy the public key hash and store it in a location that you can access from your code
Click View Private Key and copy the private key, as it is presented in PEM format, and store it in a location that you can access from your code
⚠️ Private keys permit the decryption of files. They should be stored in a secure location!
ℹ️ This page describes how to obtain public-private key pairs, which allow you to execute Confidencial decryption actions using the . To decrypt a file using the SDK, at least one public-private key pair is required. The specific key pairs that are capable of decrypting a file depend on the policy used to encrypt the file. Encryption policy details, including which keys can be used to decrypt a file are contained within the metadata of a protected file.
Open the Confidencial or go to and if you haven’t done so already
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.
There are two ways to load a device-stored key, described in the sections below:
ℹ️ When you attempt to decrypt protected content and have not loaded the decryption key(s) needed to do so, the Confidencial app will prompt you to load the required key(s)
Load the file or message you wish to decrypt in the Encryption Tools page or open a file in the PDF Protector or Image Protector
Click Decrypt. Since the private key required to decrypt hasn’t been loaded yet, you are prompted to load the key now. Click Load Key From File.
Select the requested key file and click Open
✅ Your message or file will now be decrypted and the key you loaded will remain available until you log out
ℹ️ You can load device-stored keys without attempting to decrypt a message or file via the Key Management page
Click Key Management under the Advanced section of the right sidebar menu
For each key that you want to load, click the appropriate Load Private Key File link
Select the requested key file and click Open
✅ The key you loaded will remain available until you log out
💡 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.
ℹ️ This guide shows you how to load a from your device. Unlike , device-stored keys are not automatically retrieved by the Confidencial app and thus have to be loaded by the user manually. This is an that is not enabled by default. If you haven’t opted to , you do not need to follow this guide.
Open the Confidencial or go to and if you haven’t done so already
Open the Confidencial or go to and if you haven’t done so already
💡 Confidencial’s Secure Document Send Feature can be used to create a persistent share. These shares can be sent to third parties who can then upload files once or repeatedly using the same link. Persistent sharing is fully secured with end-to-end encryption is is a great replacement for SFTP or other less secure files sharing options.
Navigate to: Document Sends > + New Document Send
Toggle: Allow participants to upload
Select applicable data label for information shared
*Optional: You can set and expiration for the share to be active by toggling Set expiration and adding a date.
Add desired recipients emails *if a new user is added it will prompt you to click Send to a new user”
Once all desired recipients are added > Send
Navigate to: Document Sends > + New Document Send
Starting a new secure document send
Select desired Files or Folders
Enter the following information:
Name: This name will appear in your Secure Doc send history list
Description: This will appear under the name in your Secure Doc history list
Message to Recipient(s): This message will be show to recipients on the email notification here they are notified that files have been shared.
View-Only: Recipients will only be able to view the contents of the files sent and not be able to download the files locally. This is the most secure sharing option. It ensures you have full control of the documents shared and enables expiration of document access as users need to use the link provided to access the contents of the files.
*Current files types supported for view-only sends are PDF & MS Office Documents
Disallow Decrypted Downloads: Recipients will only be able to access the contents for shared files using the link provided and viewing using the Confidencial web app or viewers can download and encrypted version locally and will need to decrypt using the web application or MS add-ins. This is a secure method of sharing documents used for when you do not want recipients to be able to have an un-encrypted version of the shared file saved locally.
Request Expiry: This provides the sender the option to specify an expiry time period for access to the shared files.
Data Label: Select the labels that apply to type of data in the files shared. This enables your organization to report on the type of information sent and received.
You must select one data label if this has been enabled by and admin in your org
Add Recipients: Enter the email address of desired recipient(s).
*One or many recipients can be added *Recipients DO NOT need to have a Confidencial Account to receive files
Select Send Documents
You have completed the secure doc send workflow.
💡 When looking to securely send documents to third parties or within your organization you can use Confidencial’s Secure Doc Send. Confidential Secure Document Send is designed to ensure that only authorized personnel can access documents shared with them and protects against unauthorized disclosures and data lekage. This process involves on information sent using SDS. Documents sent with Secure Doc send are automatically encrypted to the recipients of the document send. This ensure sensitive data sent is only accessible by desired parties for the desired time period.
You have received an email from noreply@confidencial.io subject: You have been added to a new persistent file share.
Open the email and click the button “Access Files”
You will be sent a verification code to your email. Enter the code provided. *Please make sure to check your spam and to make sure you have the most recent code if you are having issues.
Once authenticated a tab will open with an interface allowing you to add files.
Upload desired files > Send
Uploaded files will now be added to the persistent share and be accessible by both the sender and the requester.
NOTE: Bookmark the URL for fast access if you will be uploading multiple files overtime. Or you can access the link through the email sent.
💡 Users will be able to view their own historical doc sends and information associated.
Your historical document sends will be listed on the right hand side of the Document Send home screen. With each document send you are able to view details of what was sent and tracing activities on the documents shared.
Select a completed document send
The Recipients tab will list out the recipients of the documents and show the associated activity as “Viewed” or “Not Viewed”
If a recipient has Viewed the document you will be able to “View Activity”
This will show you the details of the activities taken by the recipients on which file.
Tracing events will show you when activities have been taken on each file sent.
Select the Tracing Events tab
Click on the file to obtain the details of the tracing events for the file
Select Tracing Map to view where the tracing events took place
On Historical Sends you will also be able to view the list of Sent Documents and any details provided with the documents sent to recipients.
Select the Sent Documents Tab to view all documents sent for that doc send
Select the Details tab to view any details provided to recipients
💡 You have received an email from telling you you have been added to a new persistent file share. This is a secure upload link where you can upload as many files up to terabytes in size through this link. Files will automatically get encrypted as soon as they are uploaded in your browser and sent to the requestor. This process is easier and more secure then other file sharing solutions or SFTP as files are encrypted client side and remain encrypted in storage. They go directly to the requesting storage provider and are not stored on a third party infrastructure.
Coming Soon
Welcome to Cloud Protector! Ready to start understanding and protecting your data, wherever it resides?
To start using Cloud Protector, you will need to do a few configuration steps. See this menu on the left side? Let's get you started, moving from bottom to top.
Visit "Analyze and Protect" to run your first scan, or set up a schedule.
Visit "Reports" to see your scan results in real-time.
Visit "Data Source Explorer" to see the current state of your data source(s) — what's protected, what's not, and where the hotspots are.
Visit "Home" to see statistics and visualizations of your overall security posture.
Visit "Settings" to and configure your protection policies.
In order to connect Cloud Protector to your AWS S3 file system, your administrator will need to log into AWS S3 and collect a few values:
Bucket: This is the name of the resource. Click "Services", then "Config", then click the name of the Config. The S3 bucket name will be displayed in the "S3 bucket" field.
Region: This is the AWS region that the bucket is in, e.g. "us-west-2". Click "Services," then "S3." The region of the bucket is in the "AWS Region" column in the Buckets list.
When you have these in hand, log into Cloud Protector and go to Settings > “Add Source.” Fill out the form.
Give your source a name that will help you recognize it.
Input the Path: the actual file path in the cloud storage that you want to analyze, encrypt, or both. Leaving this as “/” will include the whole file system.
Input the other values you have gathered.
Click “Test Connection & Save”.
Access Key Id and Secret Access Key: This pair of values is generated on the bucket itself in AWS, and you will have to create them if you haven't already. Refer to to create them.
Coming Soon
Coming Soon
User Id (Object Id)
Tenant Id
Client Id
Client Secret*
Make sure to copy and save the client secret after having followed the steps to generate it, as you cannot go back to access it once it has been created.
Create an application
Name: Confidencial CP App
Settings: account in this org only
Provide the application the required permissions (Microsoft Graph API permissions):
2.1 API Permissions > Add permissions > Microsoft Graph
2.2 Application permission > Search: Files.ReadWrite
2.3 Select Files.ReadWrite.All > Add Permissions
2.4 Delegate Permissions > Search: Files.readwrite
2.5 Select Files.ReadWrite
2.6 Select Files.ReadWrite.All > add Permissions
2.7 Application Permission > Search Sites.read.all
2.8 Select: Sites.Read.All > Add Permissions
2.9 Delegated Permissions > Search User.read
2.10 Select: User.Read
2.11 Select: User.Read.All > Add permissions
2.12 Application Permissions > User.Read.All
2.13 Select: User > User.Read.All > Add permissions
Now your new Application has all the permissions needed.
These values are now available for your newly created application.
Navigate to: App Registration > All Applications > Confidencial Cloud Protector App (Your new application)
Collect the 2 values and save on a separate sheet:
Application (Client) ID
Directory (tenant) ID
After your app is registered, you can create a client secret. Click the link next to Client Credentials (also shown) and add a secret.
Make sure to copy this value upon creation as it will be gone after it is shown to you! (Note you want the secret value not the secret ID).
When you have these in hand, log into Cloud Protector and go to Settings > “Add Source”.
5.1 Navigate to Cloud Protector > Settings > Add Source
5.2 Select Type > OneDrive
Give your source a name that will help you recognize it.
Input the Path: the actual file path in the cloud storage that you want to analyze, encrypt, or both. Leaving this as "root" will include the whole file system.
Input the other values you have gathered.
Click “Test Connection & Save”.
OneDrive Connection is now Complete.
In order to connect Cloud Protector to your OneDrive file system, your administrator will need to log into and collect a few values (Make sure to use the Azure link provided):
This is the alphanumeric Object ID of the user with admin access to the data. To locate it, go to the > Click on the User > Copy the Object ID.
An application must be created within with permissions granted to Confidencial.
Navigate to the page
Coming Soon
Coming Soon
Coming Soon
From the Encryption Tools page, choose the files and/or folders you want to protect. There are two ways to do this.
You can choose files and folders by clicking the choose files link in the input box
You can drag and drop files and/or folders onto the input box
Click Encrypt
Click Save File to choose a location to store your Confidencial-protected file
✅ You have now created a Confidencial-protected file that contains the files and/or folders you selected.
ℹ️ These instructions show you how to encrypt files and folders using the Confidencial desktop app. You can also .
Begin by opening the Confidencial desktop app and if necessary
After you have selected the files and/or folders you want to protect, that you want to be able to see the protected content
ℹ️ If you selected a single file to protect, a single .c11 file will be generated that is a protected version of the file. If you selected multiple files and/or one or more folders to protect, a file bundle will be created in the form of a .zip file that contains multiple .c11 files. In both cases (single .c11 file or .zip file containing multiple .c11 files), you will be able to decrypt the file or bundle in either the or the .
Coming Soon
Coming Soon
🔒 While this document recommends specific values for configuration options, administrators that are comfortable with AWS S3 may opt to choose different configuration options. Please consult with an AWS security expert and/or Confidencial technical staff If deviating from the options prescribed below.
Log in to your enterprise’s AWS web console and open S3
Click Create bucket
Enter new bucket settings
Enter a bucket name and select a region
🗒️ Make note of the bucket name and region that you use, as these will need to be communicated to your Confidencial technical contact to complete the set up process
Other settings can be adjusted in accordance with your enterprise’s security policies, though depending on the mode in which you configure Confidencial software to connect to your bucket, an access key with PUT and in some cases GET permissions may be required (see subsequent steps in this guide)
Click Create bucket
Click on the bucket you just created and under Permissions / Cross-origin resource sharing (CORS), click Edit
Paste in the JSON below and click Save changes
⚠️ The value for `AllowedOrigins` in the JSON above will be different for sandbox deployments. Your Confidencial technical contact will provide the correct value in these cases.
➡️ Choose the next section to follow based on whether your enterprise users will download objects from your enterprise’s S3 bucket using
Their enterprise IDP credentials (continue to next section); or
An access key stored with Confidencial (skip next two sections)
⚠️ Only follow the steps in this section if your enterprise users will download objects from your enterprise S3 bucket using credentials from your enterprise IDP
Create a new policy for bucket access. From IAM, click Policies on the left sidebar menu, then click Create policy.
Click JSON, then paste in the JSON below, replacing *<bucket-name>*
with the name of the bucket you created in the previous section, then click Next
⚠️ NOTE: Replace `aws` with `aws-us-gov` in the above policy if creating the bucket in GovCloud
For Policy name, enter confidecial-bucket-put-access
, then click Create policy
➡️ Continue to *Setting up Confidencial user bucket download access through your enterprise IDP*
⚠️ Only follow the steps in this section if your enterprise users will download objects from your enterprise S3 bucket using credentials from your enterprise IDP
Open the role that was created in the previous step in AWS IAM. From IAM in the AWS Web Console, select Roles from the left sidebar menu, search for the role, and then click on it. If the instructions in the link in Step 1 above were followed, the role will be called confidencial-users
.
Under Permissions policies, **select Add permissions > Create inline policy
Under Policy editor, select JSON
Paste the policy below into the Policy editor, replacing *<bucket-name>*
with the name of the bucket you created in the first section
Click Next
For Policy name, enter confidecial-bucket-get-access
, then click Create policy
➡️ Continue to Creating an access key for Confidencial bucket access
⚠️ Only follow the steps in this section if your enterprise users will download objects from your enterprise S3 bucket using an access key stored on Confidencial’s server
Create a new policy for bucket access. From IAM, click Policies on the left sidebar menu, then click Create policy.
Click JSON, then paste in the JSON below, replacing <bucket-name>
with the name of the bucket you created in the previous section, then click Next
For Policy name, enter confidecial-bucket-get-and-put-access
, then click Create policy
➡️ Continue to Creating an access key for Confidencial bucket access
Create a new user for bucket access. From IAM, click Users on the left sidebar menu, then click Create user.
For User name, enter confidencial-bucket-access
, then click Next
Under Permissions options, choose Attach policies directly
, then click the checkbox next to the policy you created earlier (confidencial-bucket-...-access
)
If Confidencial will upload and download via this access key, attach the confidecial-bucket-get-and-put-access
policy
If Confidencial will only upload via this access key, attach the confidecial-bucket-put-access
policy
Click Next
Click Create user
Select the user you just created (confidencial-bucket-access
) and under Security credentials / Access keys, click Create access key
For Use case, select Application running outside AWS
, then click Next
For Description tag value, enter Confidencial bucket access
, then click Create access key
🗒️ Make note of the Access key and Secret access key. This is the only time that you will be able to see the secret key. Make sure that the secret key is stored in a secure location; this information will need to be securely transmitted to your Confidencial technical contact to complete the set up process.
Click Done
✅ This completes your portion of document request S3 bucket configuration. You will now need to securely transmit the following information to your Confidencial technical contact: bucket name, bucket region, access key, and secret access key.
ℹ️ This page describes how to create an AWS S3 bucket to store information and files that are securely transmitted to your enterprise from external users via Confidencial’s feature
If you haven’t done so already, create a user pool in AWS Cognito to enable your enterprise’s users to download directly from the S3 bucket using their enterprise IDP credentials. See .
ℹ️ These instructions cover how to provision the Confidencial Key Server (CKS) in your server hosting environment and include the following primary steps:
Instantiate a MySQL database to serve as the CKS DB. There are multiple options to host the CKS DB, including:
An existing MySQL server
A MySQL server running in a Docker container
A MySQL server running in an AWS Relational Database Service (RDS) instance
ℹ️ The CKS DB instance must be accessible from the CKS web server, which you will configure in the subsequent sections of this document.
Once your CKS DB instance is running, create a database within the server. Do this by logging in to your MySQL DB server and executing the command below.
Replace dbname
in the command above with the name you wish to use for the CKS DB
After the DB has been created, make sure you create a DB account that has full access to the database (the ability to create and alter tables and the ability to read data from and write data to tables). This can be done by executing the MySQL command below.
Obtain a token to access Confidencial’s container registry using the ID and secret provided by Confidencial. Replace <your key ID>
and <your secret>
in the shell commands below with the Confidencial-provided ID and secret, respectively. Execute the commands below.
➡️ Executing the commands above will result in the CKS docker image being pulled into your current directory. You will now proceed to push this image to your preferred container hosting environment (described in the next section).
Push the CKS container image to your container hosting environment. There are multiple options for hosting docker images, including:
A Kubernetes cluster
AWS’s Elastic Container Service (ECS)
Within an AWS Elastic Compute Cloud (EC2) instance
⚠️ Note that values for `KNEX_USER`, `KNEX_PASSWORD`, and `KNEX_DB_NAME` are wrapped in single quotes. This is done to ensure that special characters and spaces are handled properly.
Launch the CKS container.
⚠️ While users in your enterprise need to be able to reach the CKS web server (port 443) from their client machines, users do not need direct access the the CKS DB. The CKS DB need only be accessible from the CKS web server.
⚠️ You may choose to make the CKS web server available outside your enterprise’s firewall. This permits users to use Confidencial from external networks without the use of a VPN. However, doing so increases the exposure of the CKS, making it more susceptible to attack.
Configure your container hosting environment to route inbound requests from port 443 (TLS) of an enterprise-accessible URI to port 8000 of the CKS web server container.
✅ This completes your portion of CKS set up. Confidencial will ask you to provide the URI of the CKS web server to complete the deployment.
ℹ️ The CKS requires users to authenticate using credentials provided by your enterprise identity provider (IDP). Follow the link below to register the CKS as an application within your IDP.
✅ This completes your portion of CKS set up. Confidencial will ask you to provide the URI of the CKS web server to complete the deployment.
Replace dbname
with the DB name you assigned and replace username
with the user name of the DB account to which you want to grant full access
➡️ Next, Confidencial will provide you with a script to create the necessary tables and relationships in the database. This is referred to as a database migration. See
If not already installed, download the
ℹ️ If you are hosting your own AWS container registry (AWS ECR), see for how to push the pulled key server image to your registry
Set the following environment variables for the CKS container. Replace <your DB URI>
, <your DB port>
, <your DB username>
, <your DB password>
, and <your DB name>
with the values necessary to connect to the database instantiated .
This documentation is coming soon
This documentation is coming soon
🔒 While this document recommends specific values for configuration options, administrators that are comfortable with AWS Cognito may opt to choose different configuration options. Please consult with an AWS security expert and/or Confidencial technical staff If deviating from the options prescribed below.
Open Cognito in the AWS Web Console
Click Create user pool
Under Provider types, check the Federated identity providers option
Under Cognito user pool sign-in options, check the User name option
Under Federated sign-in options, check the OpenID Connect (OIDC) option
Click Next
Under the Configure security requirements page, configure the following options:
Password policy: Leave default values (this will not be used since your users will be using their enterprise credentials, and not Cognito-managed credentials, to authenticate)
Multi-factor authentication: No MFA (Cognito-based MFA is not recommended as you may enforce MFA through your IDP instead)
Enable self-service account recovery: Uncheck (Cognito account recovery is not needed because account recovery will be managed through your IDP)
Click Next
Under the Configure sign-up experience page, configure the following options:
Enable self-registration: Uncheck (new account creation will be managed through your IDP)
Allow Cognito to automatically send messages to verify and confirm: Uncheck (new account creation will be managed through your IDP)
Click Next
Under the Configure message delivery page, select Send email with Cognito (note that these settings are not relevant since Cognito will not need to send emails to your enterprise users)
Click Next
Under the Set up OpenID Connect federation with this user pool section, enter the following values that can be obtained from the Confidencial application configuration in your IDP:
Provider name: Enter a name to refer to your IDP instance (e.g. Entra ID - Production
or Okta - Sandbox
)
Client ID: Enter the client ID from your IDP’s Confidencial application
Client Secret: Enter the client secret from your IDP’s Confidencial application
Authorized scopes: openid profile email offline_access
Attribute request method: GET
Retrieve OIDC endpoints / Setup method: Auto fill through issuer URL
Issuer URL: Enter the issuer URL from your IDP’s Confidencial application
User pool attribute / email: email
Click Next
Under the Integrate your app page, enter the following values:
User pool name: confidencial
Domain type: Use a Cognito domain
Cognito domain: Enter a globally-unique name for your domain (e.g. confidencial-yourenterprisename
)
App type: Public client
App client name: confidencial
Client secret: Don't generate a client secret
Allowed callback URLs: https://my.confidencial.io/auth?ref=cognito
⚠️ NOTE: This URL will be different if you are operating in a sandbox environment. Please contact your Confidencial technical support representative if you are using a sandbox environment.
Under Advanced app client settings / Identity providers, click the “X” to remove the Cognito user pool option, leaving only the identity provider you named earlier
Under Advanced app client settings / OpenID Connect scopes, click the “X” to remove the Phone option, leaving only the OpenID and Email options
Click Next
Review that your configuration is correct and click Create user pool
Open Cognito in the AWS Web Console
Click Identity pools in the left sidebar menu
Click Create identity pool
For User access, select Authenticated access
For Authenticated identity sources, select Amazon Cognito user pool
Click Next
For IAM role, select Create a new IAM role
For IAM role name, enter confidencial-users
Click Next
Under the Connect identity providers page, enter the following values:
User pool ID: Select the ID of the user pool that you created in the previous section
App client ID: Select the ID of the application you created in the previous section
Role selection: Use default authenticated role
Claim mapping: Inactive
Click Next
Under the Configure properties page, enter the following values:
Name: confidencial-users
Click Next
Review that your configuration is correct and click Create identity pool
⚠️ If running a migration on a database with existing data, BE SURE TO RUN A BACKUP/SNAPSHOT OF YOUR DATABASE BEFORE PROCEEDING
In addition to target database access, this machine must also have internet access to be able to install additional packages
We will refer to this machine as the migration machine. The migration machine can be the database server itself, but it doesn’t need to be.
Unzip the migration files in a directory on the migration machine
We will refer to this folder as the migration folder
From the migration folder, run the following command
This will create a file in the migration folder called .env.kss.production
Open .env.kss.production
in a text editor and add the connection parameters for the target database
This file tells the migration code how to connect to the target database
⚠️ Note that values for `KNEX_USER`, `KNEX_PASSWORD`, and `KNEX_DB_NAME` are wrapped in single quotes. This is done to ensure that special characters and spaces are handled properly.
From the migration folder, run the following commands
These commands will install the necessary packages from the internet and then execute database commands to create (or update) the tables in the target database
Click Microsoft Entra ID
Click App registrations from the side menu
Click New Registration from the top toolbar
Ensure the following settings are entered:
Name: Confidencial-OPKSS
Supported account types: Select either “Accounts in this organizational directory only,” “Accounts in any organizational directory,” or Accounts in any organization directory and personal Microsoft accounts,” depending on who you want to be able to join your Confidencial organization
Redirect URI: Choose “single-page application (SPA)” in the Select a platform drop down menu and enter https://my.confidencial.io/auth-management
in the input box
Click Register
Click Manifest (under Manage), then
Change the value of acceptMappedClaims
(Line 3) from null
to true
Click Save
Return to the main Entra page and click Enterprise applications from the side menu
Click Confidencial-OPKSS in the list of applications
Click Single sign-on (under Manage)
Click the Edit button for Attributes and Claims
Click Add new claim
Input a Name of https://confidencial.io/email
, Source will be Attribute
and Source attribute will be user.mail
.
Click Save
Click Add new claim
Input a Name of org_id
, Source will be Transformation
, and data will be entered like the following values:
Transformation: RegexReplace()
Parameter 1: Attribute
Attribute name: user.city
Regex pattern: ^.*$
Replacement pattern: This value will be provided by your Confidencial support representative
Click Add to add the transformation
Click Save
Return to the main page for the enterprise application Confidencial-OPKSS
Click Properties (under Manage) from the side menu
If you want to specify the users that can log in to Confidencial, set Assignment required to “Yes,” otherwise, all users* will be able to log in to Confidencial
ℹ️ All users with a supported account type specified in Step 5.b above
ℹ️ This completes creation of the Entra ID application and generates a *Client ID* that must be securely transmitted to Confidencial during account set up (along with the *Entra Domain*). Optionally, you may continue to the next section to configure automatic user and group provisioning via SCIM.
Click Enterprise applications from the Entra ID main menu
Click New application
Click Create your own application
For the name of the application, enter Confidencial-OPKSS-SCIM
Select Integrate any…(Non-gallery) from the list of options and click Create
Select Users and groups (under Manage) from the side menu
Associate users and groups to this new application. These are the users and groups that will be automatically synchronized with Confidencial.
Click Provisioning (under Manage) from the side menu. You may have to select Provisioning (under Manage) a second time to display the Provisioning Mode setting.
Set Provisioning Mode to Automatic
Under Admin Credentials, enter the following settings:
Tenant URL: https://opkss.confidencial.io/{orgId}/scim/v2/?aadOptscim062020
, where {orgID}
is your organization’s ID, which is provided by your Confidencial support representative
ℹ️ The Entra ID implementation requires the `?aadOptscim062020` parameter to achieve full SCIM compliance.
Test your connection settings — If there are any issues here please reach out to a Confidencial support representative for further assistance.
Click Save
Click Overview
Click Start provisioning
ℹ️ By default, the provisioning interval is set to 40 minutes; this, as well as the ability to send an email notification when a failure occurs, can be adjusted by clicking the Settings dropdown menu.
ℹ️ This document shows you how to connect to your identity provider, allowing your enterprise’s users to log in to Confidencial using their existing accounts.
⚠️ Please contact your Confidencial support representative before beginning this process to ensure you have the proper components to proceed
The details of how to connect to your identity provider (IDP) vary depending on the IDP being connected, but in most cases, the process amounts to creating an application within your IDP and then assigning users to that application. See the links below for how to connect to your IDP.
Log in to your Okta instance’s admin portal
Click Applications under the Applications item in the side menu
Click the Create App Integration button
Select OIDC - OpenID Connect and Web Application for Sign-in method and Application type, respectively; click Next
Ensure the following settings are entered:
App integration name: Confidencial
Grant type: Authorization Code (the only option that should be selected)
Sign-in redirect URIs: https://auth.confidencial.io/login/callback
Sign-out redirect URIs: https://my.confidencial.io
⚠️ Redirect URIs will be different than those listed above for sandbox deployments. Your Confidencial technical contact will provide these URIs in these cases.
For Controlled access, select either “Allow everyone in your organization to access” or “Limit access to selected groups,” depending on who you want to be able to log in to Confidencial.
If you selected “Allow everyone…,” leave “Enable immediate access with Federation Broker Mode” selected if you want everyone in your organization to be able to access Confidencial. Deselect “Enable immediate access with Federation Broker Mode” if you want to specify the users and groups that can access Confidencial.
If you selected “Limit access…,” enter the group(s) you’d like to access Confidencial under Selected group(s).
Click Save
ℹ️ This completes creation of the Okta application and generates a Client Secret that must be securely transmitted to Confidencial during account set up (along with the Okta Domain and Client ID).
➡️ Proceed to the next section, *Creating Confidencial roles for Okta users*
Click Groups under the Directory item in the side menu
Click Add Group
In the Name field, enter a name for the role (Okta group). In this example, we create a role called C11-Admins
.
In the Description field, enter the Confidencial permissions you would like to grant to members of this role
crud:config-org
: Allows an administrator to create, read, and delete admin config settings for an organization
crud:invitations-org
: Allows an administrator to create, read, and delete invitations for an organization
crud:signature-keys-org
: Allows an administrator to create and update (replace) electronic signature keys from all members in an organization
crud:groups-org
: Allows an administrator to create, read, update, and delete groups within an organization
Click Save
With the Okta group created, take note of the Okta group ID; this will be needed in the next section, Create the Okta authorization server for Confidencial
To get the group ID of the group you created, go to the group in Okta and note the last part of the URL
In the example above, the group ID is 00g9372cmsozlGYI25d7
Add the users to the group to which you would like to assign these permissions
🔁 Repeat Steps 1-7 above for each role you would like to define in the Confidencial system. You can create up to 100 roles for Confidencial users, roles can contain any combination of permissions, and users can belong to any combination of roles.
➡️ Proceed to the next section, Creating the Okta authorization server for Confidencial
Click API under the Security item in the side menu
Click Add Authorization Server
For Name, enter Confidencial
and for Audience enter api://confidencial.io
Click the Scopes tab, then click Add Scope
Enter the following values:
Name: groups
Display phrase: groups
Description: Allows group membership to be passed in token
Use default values for the other fields, as shown below
Click Access Policies, then click Add New Access Policy
Enter the following values:
Name: Default
Description: Default
Assign to: Add the Okta application you created in the previous section, Creating an application in Okta
Add a rule to govern access to this authorization server, ensuring that “authorization code” is permitted; set access token and refresh token lifetimes as desired
Click the Claims tab, then click Add Claim
Enter the following values:
Name: permissions
Value: Arrays.flatten(getFilteredGroups({"group-id-1", "group-id-2", ... , "group-id-n"}, "Arrays.flatten(group.description)", 100))
Replace "group-id-1", "group-id-2", ... , "group-id-n"
in the above statement with the list of group IDs you created in the section above, Creating Confidencial roles for Okta users
Group IDs should be wrapped in double quotes (”
) and separated by commas (,
), with the entire list of group IDs wrapped in curly braces ({ }
)
Use default values for the other fields, as shown below
Click Create
➡️ Proceed to the next section, Assigning users to an application in Okta
ℹ️ These steps are not necessary if you left “Enable immediate access with Federation Broker Mode” selected in Step 6 of Creating an application in Okta above.
Click Applications under the Applications item in the side menu
Click Confidencial in the list of applications
Click the Assignments tab
Click Assign to add users and groups that can log in to Confidencial
✅ This completes the setup of Okta for use with Confidencial. You will now work with the Confidencial team to securely transmit application details.
Click Microsoft Entra ID
Click App registrations from the side menu
Click New Registration from the top toolbar
Ensure the following settings are entered:
Name: Confidencial
Supported account types: Select either “Accounts in this organizational directory only,” “Accounts in any organizational directory,” or Accounts in any organization directory and personal Microsoft accounts,” depending on who you want to be able to join your Confidencial organization
Redirect URI: Choose “Web” in the Select a platform drop down menu and enter https://auth.confidencial.io/login/callback
in the input box
Click Register
Click App registrations from the side menu
Click Confidencial in the list of applications (you may need to select the All applications tab to view it)
Click Token configuration (under Manage) from the side menu
Click Add optional claim
Select ID, then select email, and then click Add
Check the box to enable email permission, then click Add
Return to the main Entra menu
Click Enterprise applications from the side menu
Click Confidencial in the list of applications
Click Properties (under Manage) from the side menu
If you want to specify the users that can log in to Confidencial, set Assignment required to “Yes,” otherwise, all users* will be able to log in to Confidencial
Click App registrations from the side menu
Click Confidencial in the list of applications (you may need to select the All applications tab to view it)
Click Certificates & secrets (under Manage) from the side menu
Click Add new client secret
Description: Confidencial IDP integration
Expires: 730 days (24 months)
Click Add
⚠️ Make note of Value, as this client secret will need to be securely transmitted to Confidencial and is only viewable during initial creation
ℹ️ This completes creation of the Entra ID application and generates a client secret that must be securely transmitted to Confidencial during account set up (along with the Entra Domain and Client ID).
➡️ Proceed to the next section, Assigning users to an application in Entra ID
ℹ️ These steps are only necessary if you selected “Yes” for Assignment required in Step 10 above.
From the Microsoft Entra ID home screen, click Enterprise applications from the side menu
Click Confidencial in the list of applications
Click Users and groups (under Manage) from the side menu
Click Add user/group to add users and groups that can log in to Confidencial
✅ This completes the setup of Entra ID for use with Confidencial. You will now work with the Confidencial team to securely transmit application details.
Click Users from the side menu
Apply any filters wanted when narrowing down the list of users that will have a set of permissions OR permission in general
ℹ️ Admins may want to exclude the Guest user type here potentially as an example
Click Download users
Input a name for the file and click Start download
Click File is ready! Click here to download
once file is complete
Open the CSV file as comma delimited starting at row 1
Add a new column to the end of the table called permissions
Add comma separated permissions as a single string for each user that should have the related permissions in Confidencial - example: crud:members-org, crud:groups-org
ℹ️ Users with their permissions field empty will have no admin permissions when script is run later
Save your changes once complete.
Complete steps 2-7 for as many other csv files you might want to create.
Click App registrations from the side menu
Click Confidencial in the list of applications (you may need to select the All applications tab to view it)
Click API Permissions (under Manage) from the side menu
Click Add a permission
Select Microsoft Graph from the list of options, then click Application permissions
In the Select permissions search box, search for permission Directory.ReadWrite.All
Expand Directory by clicking the “>” symbol
Select the checkbox for Directory.ReadWrite.All
and click Add permissions
Click Grant Admin Consent for Confidencial and then Yes to confirm this action
Run createExtProp.ps1
using PowerShell to create the permissions extension property
ℹ️ Contact your Confidencial support representative to obtain the PowerShell scripts
You will need to supply the tenant ID, client ID, app ID, and client secret corresponding to your app registration for Confidencial as command-line arguments to the script
If you do not know your client secret, you will need to create a new one for the app registration; be sure to keep your original secret that was created during the initial set up of the app registration
Copy the extension property ID once created and save for a later step
This will be under name and will take the form extension_*<hexidecimal code>*_permissions
Click Token Configuration (under Manage) from the side menu
Click Add optional claim
Select the ID radio button then select the extn.permissions
option in the list
Click Add button
Run setExtPropValues.ps1
using PowerShell to set the permissions extension properties values
Execute this script for each CSV file created for permissions assignment
✅ This completes adding permissions to your users for when they log into Confidencial
ℹ️ This guide walks through the process of setting up an AWS Cognito user pool to enable your enterprise’s users to download directly from the S3 bucket that stores data using their enterprise identity provider (IDP) credentials. This approach allows the document request feature to function without requiring Confidencial to store credentials that are capable of downloading objects from your S3 bucket.
⚠️ If you have not already done so, follow the instructions in to connect your enterprise’s IDP before continuing with the steps below
ℹ️ See for the steps that were taken to create the Confidencial application in your IDP
ℹ️ When Confidencial server software for the first time or upgrading an existing Confidencial instance, you will occasionally need to run a database migration. Database migrations create (or update) the table structure within a database. Migrations may need to be run for the or the . In either case, Confidencial will provide the requisite files to run the migration, usually in the form of a zip file.
⚠️ These instructions assume the database server has been instantiated, the database within that server has been created, and the database account you are using to access the database has full permissions on the database. See the relevant deployment instructions for more detail on how to do this.
on a machine that has network access to the target database
✅ This completes database migration. If you encounter issues during this process, please .
Log in to the
ℹ️ Most organizations will want to select “Accounts in this organizational directory only,” as users outside your organization can log in to Confidencial via their own or via an .
Token: This is the SCIM token created by signing into application and generating a token under the organization settings page as an admin.
ℹ️ These steps allow you to define Confidencial “roles” that allow you to grant various to your users by using Okta groups. The Confidencial permissions granted are determined by the description fields of the Okta groups to which each user belongs.
ℹ️ For a Confidencial user to be able to exercise any of the permissions described below, they must be within the Confidencial system
crud:members-org
: Allows an administrator to
crud:recovery-keys-org
: Allows an administrator to create, read, and deactivate that are used by an organization
read:events-org
: Allows an administrator to see all within an organization
crud:encryption-keys-org
: Allows an administrator to create and update (replace) for all members in an organization
crud:groups-scim-tokens-org
: Allows an administrator to create, read, update (replace), and delete tokens that are used by the enterprise’s identity provider to make calls to the SCIM endpoints of
Log in to the
ℹ️ Most organizations will want to select “Accounts in this organizational directory only,” as users outside your organization can log in to Confidencial via their own or via an .
All users with a *supported account type* specified in Step 5.b above
This documentation is coming soon
Click Members under the Organization Admin section in the sidebar menu
For the appropriate user, under the Role column, click the down arrow next to “Member” and then click Change Role to Admin
⚠️ To use the following method, you will need to have the appropriate administrator privileges within your Microsoft environment
From the Apps menu, click Admin
Click Show all from the left sidebar menu
Under Settings, click Integrated apps
Click Upload custom apps
For App type, select Office Add-in
Under Choose how to upload app, select Upload manifest file (.xml) from device and choose the manifest file provided by Confidencial
Click Next
Choose the user(s)/group(s) that you would like to push the add-in to
Click Next
You will now see the capabilities required by the add-in. Click Next to proceed.
Confirm your selections and click Finish deployment
Once the deployment is complete, click Done
✅ The add-in will now be pushed to the users you selected. Repeat this process for each manifest file that was provided by Confidencial.
Users are added to the organization via your IDP “on the fly” (at the time of their first login)
If your organization does NOT use a third-party IDP:
Click Add Member
Enter the email addresses of the members you wish to add. You may enter email addresses manually or load a list of email addresses from a CSV file (one email address per line).
Click Send Invites
✅ The added members will now receive invitation emails
ℹ️ This feature is only available to within a
⚠️ You must be a organization administrator to designate other members as organization administrators. “Root” organization administrators (the initial set of org admins) are designated by Confidencial staff at the time of organization creation. If you need Confidencial to set a new root administrator, contact .
✅ The user is now able to access administrator functions. NOTE: If you are using a , you will also need to assign this user specific .
ℹ️ These instructions cover how to “push” Confidencial’s add-ins for Microsoft Office using the Office Admin Center and “manifest” files provided by Confidencial. You can also push add-ins by while logged in as a user with administrator privileges.
Log in to Office Admin Center at
📨 Contact us at if you do not have the manifest file(s)
ℹ️ This feature is only available to within a
ℹ️ If your organization uses a :
However, you may still “pre-load” users, generating their encryption keys before their first login; follow the instructions
To add members to your organization, follow the instructions
⚠️ When you use this method to add a member to an organization that does not host its own , a is generated for their account so users can immediately encrypt content for them. This temporary key is stored in Confidencial’s secure key server. Once the invited user registers their account, they will generate a more secure . All subsequent encryptions for them will use the split key. In organizations that host their own CKS, temporary key pairs are stored in the organization’s CKS.
Once to the desktop or web app, click Members under Organization Admin in the sidebar menu
If you do not see Send Invites but instead see Add Members and Generate Keys, then you are using a third-party IDP. To pre-load members, follow the instructions .
This policy determines whether Confidencial users outside your organization can search and encrypt for members within your organization. If this policy is disabled, only users inside your organization can encrypt for other users in your organization. This policy does not impact the ability of users in your organization to encrypt for users outside your organization.
ℹ️ Organization-level policies are settings within the Confidencial platform that apply across all members and usage within a . These policies are configured by Confidencial at the time of organization creation. Subsequent changes to policies must be made by contacting .
This policy determines if users inside your organization are able to see a listing of other members in the organization. If this policy is enabled, organization members are able to see other members of the organization by . If this policy is disabled, users must enter the complete email address of another user to be able to encrypt content for them.
Users are added to the organization via your IDP “on the fly” (at the time of their first login)
If your organization does NOT use a third-party IDP:
Click Add Member
Enter the email addresses of the members for which you wish to pre-load and generate keys. You may enter email addresses manually or load a list of email addresses from a CSV file (one email address per line).
Click Add Members and Generate Keys
✅ The added members will now have keys generated for them, they will now appear in the organization’s directory listing, and other users may protect content for them immediately.
ℹ️ If your organization uses a :
However, you may still “pre-load” users, generating their encryption keys before their first login; follow the instructions
To add members to your organization, follow the instructions
⚠️ When you use this method to add a member to an organization that does not host its own , a is generated for their account so users can immediately encrypt content for them. This temporary key is stored in Confidencial’s secure key server. Once the invited user registers their account, they will generate a more secure . All subsequent encryptions for them will use the split key. In organizations that host their own CKS, temporary key pairs are stored in the organization’s CKS.
🔑 NOTE: You need to be logged in as an with crud:encryption-keys-org to be able to use this feature, which generates keys for other members of the organization.
Once to the desktop or web app, click Members under Organization Admin in the sidebar menu
If you do not see Add Members and Generate Keys but instead see Send Invites, then you are not using a third-party IDP. To add members, follow the instructions here: .
Create a new or select an existing M365 account from which you want Confidencial to send email notifications
Expand the Identity menu > expand Applications> select App registrations > New registration
Enter the following values:
Name: Confidencial
Supported account types: Accounts in this organizational directory only
Redirect URI (optional): Leave blank
Click Register
Select Certificates & secrets > Certificates > Upload certificate
Upload the certificate that is provided by Confidencial
Click Add
Click Overview and make note of the application’s (client) ID. This ID will be used later when restricting application permissions.
ℹ️ These instructions are derived from Microsoft documentation found here
Click Add a group, select Mail-enabled security, and click Next
Enter the following values:
Name: Confidencial notifications
Description: Mailboxes used to send notifications on behalf of the Confidencial app
Click Next
Assign owners to the group - these are users that have the ability to manage group settings
Click Next
Add the member that owns the mailbox to be used for Confidencial notifications
Click Next
For Group email address, enter confidencial
(@yourdomain.com
)
Leave the Communication checkbox unchecked
Check the Approval checkbox to limit membership to the group
Click Next
Click Create group, then click Close
Create an application access policy by executing the command below in Exchange Online PowerShell. Replace app-id
with the application (client) ID noted in the first section above. Replace yourdomain.com
with your domain. 1.
Test the access policy with the command below. Replace yourmailbox@yourdomain.com
with the email address of the mailbox to be used for Confidencial notifications (note that this is different from the group email address you specified in the previous step). Replace *app-id*
with the application (client) ID noted in the first section above. Repeat this command using an email address that is NOT the one to be used to send Confidencial notifications.
If the access policy is correct, the output of the above command should include AccessCheckResult : Granted
. If you run the above command with an email address that is NOT in the security group, you should see AccessCheckResult : Denied
.
⚠️ NOTE: Changes to application access policies can take longer than one hour to take effect in Microsoft Graph REST API calls, even when `Test-ApplicationAccessPolicy` shows positive results. If there is concern about exposing unnecessary access to Graph API calls, it is recommended to wait at least one hour before proceeding to the next section.
Expand the Identity menu > expand Applications > select App registrations
Select the Confidencial app registration that you created in the first section. You may need to click the All applications tab for this application to appear in the list.
Under Manage, click API permissions, then click Add a permission
Click Microsoft Graph
Select Application permissions
In the Select Permissions search box, enter Mail.Send
Expand the Mail result that appears, click the checkbox next to Mail.Send, then click Add Permissions
Click Grant admin consent for… and click Yes on the resulting confirmation dialog
Sender email address (email address from which notifications are sent)
Entra tenant ID
Entra Confidencial client (app) ID
On the Recovery Keys page, click Create Recovery Key
Click Download Recovery Key and choose a place to save the recovery key
⚠️ This will download a private key that can be used to recover (decrypt) any content that is encrypted by or for any member of your organization. Since this private key is generated on your machine, this is the only time the private key is made available for saving (downloading). It is of utmost importance to save this key file in a reliable, secure location.
✅ This creates a recovery key that will be applied to all content encrypted by or for the organization. The public key certificate of the recovery key is now visible on the Keys page in the Organization Recovery Keys table.
ℹ️ These instructions are derived from Microsoft documentation found
Log in to the
In the , click Recipients > Groups > Mail-enabled security
ℹ️ These instructions are derived from Microsoft documentation found
Connect to Exchange Online PowerShell. For details, see .
⚠️ NOTE: It is likely you will need to execute commands to allow for script execution. See for details.
Log in to the
✅ This completes customer-side configuration for use of a customer-owned mailbox to send Confidencial notifications. Confidencial staff will complete the remainder of the needed configuration changes. Confidencial will send you a asking for the following:
ℹ️ This feature is only available to within a
Once to the desktop or web app, click Recovery Keys under Organization Admin in the sidebar menu
ℹ️ These instructions show you how to view usage of Confidencial products within your organization
Click Analytics under the Organization Admin section of the sidebar menu
You will be able to see all Confidencial activity within your organization. You can filter data based on organization member and date range.
Click on a column within a graph to see a breakdown of usage for a given Confidencial product
You can click Details to see a table (list) view of all log events for the specified date range
Back on the main Analytics page, you can click Download CSV to get a comma-separated values (CSV) export of the event log data for your organization
ℹ️ This feature is only available to within a
Open the Confidencial or go to and