SigningHub allows multiple storage areas to save the documents transactions (revisions), templates, and library files. During deployment, the SigningHub Installer gives you three different options to choose the one for saving this data in an encrypted format, i.e.:

• File System Storage
• Azure Blob Storage
• Database Storage

The option selected during installation, is shown read-only on the SigningHub Admin interface. However the related details are editable and can be updated as required. Similarly, you can also configure document locking settings from here that require an invisible signature on the PDF.

Document Settings
Fields	Description
Storage
File System Storage	When the "File System Storage" option is selected from the SigningHub Installer: SigningHub Installer will require a valid document storage directory that could be used to store all the data, and ensures that the required permissions (rights) are available on the folder.  All the data will be stored on I/O. Whenever a new document is uploaded from a user end (i.e. SigningHub Desktop Web, SigningHub Mobile Web), a new folder with their "package ID" name is created (inside the document storage path) to store all its revisions with their unique GUID names, and its workflow evidence report that is placed upon workflow completion. Similarly when a document is added from a library or it is added in a personal or enterprise library, then it is always saved inside the "Library" folder of the document storage path. The same goes for creating personal and enterprise templates, they are saved inside the "Templates" folder of the document storage path. The actual path of document directory is editable in SigningHub Admin.
Azure Blob Storage	When the "Azure Blob Storage" option is selected from the SigningHub Installer: SigningHub Installer will require a valid Azure storage account to store all the data. When specified, an Azure blob connector will be created (inside SigningHub Admin) with the Azure account details upon successful installation. All the data will be stored on Azure Blob Storage. Whenever a new document is uploaded from a user end (i.e. SigningHub Desktop Web, SigningHub Mobile Web), a new folder with their "package ID" name is created (inside the Azure Blob Container) to store all its revisions with their unique GUID names, and its workflow evidence report that is placed upon workflow completion. Similarly when a document is added from a library or it is added in a personal or enterprise library, then it is always saved inside the "Library" folder of the Azure Blob Container. The same goes for creating personal and enterprise templates, they are saved inside the "Templates" folder of the Azure Blob Container. The Azure Blob connector details are editable in SigningHub Admin.
Database Storage	When the "Database Storage" option is selected from the SigningHub Installer: All the documents, library items, and template related documents will be stored on database. The documents are saved in the "DocumentRevision" database table.  The library items are saved in the "DocumentLibrary" database table.  The template related documents are saved in the "TemplateDocument" database table.
Lock PDF Fields
Lock PDF fields by adding invisible signature in the document	Tick this option to configure documents locking settings. For document locking, an invisible signature is added on the PDF file after the last recipient so that it cannot be amended later.  A couple of fields will appear, i.e. "Signing Server" and "Signing Service Profile ID". The "Signing Server" field will display the list of ADSS Server connectors. Select the one to compute  PAdES Part 2 invisible signatures for the PDF documents to be locked. Click  to view the details of the selected connector. In the "Signing Server Profile ID" field, specify the ID or name of the profile that has been created in the ADSS Signing Server for invisible signatures, i.e. adss:signing:profile:001 When configured, system will be automatically lock those documents having form fields: In which "Document Locking" option is enabled, and Whose workflows are complete, and Irrespective of last recipient's action (i.e. signing, declining, reviewing, editing, etc.)  If you keep this option un-ticked, documents auto locking will not be triggered as per the above mentioned conditions and hence no invisible signatures will be added on the PDF documents.

1. Click the "Configurations" option from the left menu.
2. Click the "Document Settings" option.
   The "Document Settings" screen will appear displaying the selected storage option from the SigningHub Installer in read-only mode. See the "Document Settings" table above for fields description.
3. In case of File System Storage, edit the Document Storage Path as required.
   In case of Azure Blob Storage, change the Azure Blob connector as required.
4. Set the PDFs locking configuration as required.
5. Click the "Save" button.
6. Click the "Publish Changes" button from the top right corner, to make these configurations effective on the front-end (SigningHub Desktop Web).