Docs (Advanced): Seal files

Sometimes you may want to prevent clients from making further changes to a document. Or you’re working on a file and don’t want the client to accidentally delete or move it. You could place it in a top-level folder with a Client can view access level. Or, you can seal it instead – below we will tell you how.

Before you start

Sealing leaves the document in its location, but the client cannot delete, edit or move it to another folder:

  • You can seal any document stored in a folder with Client can view and edit  access level.
  • You can seal a subfolder but it means sealing all files within it. The client will not be able to upload documents to the sealed folder.
  • You can't seal a top-level folder with Client can view and edit  access level. It means that you can’t completely restrict uploading docs: even if all subfolders inside the folder are sealed, clients can upload documents to the root.   
  • If a sealed document or folder is moved to a top-level folder with a Client can view or a Private access level, it becomes unsealed.
  • If a document is moved from a sealed folder, it becomes unsealed.

Seal from the web portal

To seal documents, make sure they are stored in a top-level folder with a Client can view and edit access level, select the checkbox to the left of the documents you want to seal, then click Seal above. Or seal the whole folder so that all the documents inside it become sealed.

You can also seal a document by clicking on the three dots to the far right of the name of the document, and then selecting Seal.

When you no longer need to restrict your clients from managing specific documents, unseal them by selecting the files or folders and clicking the Unseal button above.

If you want to unseal a single file, you can also click on the three dots icon to the far right of the document’s name, then select Unseal.

Seal from the Windows app

Right-click a file on your TaxDome Drive and select Seal document.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.