DocuSanad

Support

Getting help with DocuSanad

Most problems are one of six things. Start here, and email us if none of them fit.

Getting started

Installing and setting up

  1. 1

    Install the app

    A tenant administrator uploads the package to your App Catalog and deploys it, then adds the app to the site where you want DocuSanad to run.

  2. 2

    Run Setup

    Add the DocuSanad Setup web part to a page and run it. This needs Full Control on the site. It creates the library, columns, views, lists and security groups.

  3. 3

    Add the Explorer

    Put the DocuSanad Explorer web part on a page and point it at the library Setup created. Configure grouping in the property pane.

  4. 4

    Assign licences

    An administrator assigns seats in the Microsoft 365 admin centre. Anyone without a seat gets the Free tier.

Troubleshooting

Common issues

Setup says I need site owner permissions

Provisioning creates lists, columns and a content type, which requires Full Control on the site. Ask a site owner to run Setup once; everyday use does not need those rights.

The Explorer says it cannot read the library

Check that the library name in the web part properties exactly matches the one Setup created, and that Setup has been run on this site. The Setup web part reports which pieces are missing.

Paid features are not showing

Confirm a seat has been assigned to your account in the Microsoft 365 admin centre, then reload the page. Licence state is resolved once per session.

Approval emails are not arriving

DocuSanad sends through SharePoint’s own mail service, which only delivers to recipients inside your tenant. Check the approver has an email address on their profile, and check junk mail.

A document will not delete

That is usually correct behaviour. Check whether it is under legal hold, or carries a Microsoft Purview retention label or record declaration. The Compliance dashboard shows which of these applies.

AI classification returns a connection error

Almost always CORS. Your proxy must allow your SharePoint origin exactly, with no trailing slash. Call the proxy’s /api/health endpoint first to confirm it is configured.