Control who can reach every document
Access in DocuPro is not all-or-nothing at the repository. A user's reach is decided by their identity, their group, the folders they are granted, and the metadata on the document itself — and the answer is the same in every part of the application.
Four layers, one answer
A rule written once protects millions of documents
Because rules key off index values, you never grant access document by document. Add an adjuster to the Claims Intake group and set their employer; the rule does the rest — today and for every claim filed tomorrow.
The same rules apply to search results, workflow queues, printing, and export. A document a user cannot see never appears anywhere in the application.
Enforced everywhere, not just at the front door
Every version kept, original retained
Annotations, stamps, signatures, page changes, and workflow stage transitions are recorded against the document. Version history with revert means nothing is overwritten, and the original as captured is always available.
Security FAQ
What is index-based security?
A security rule that uses the values on the document itself — for example “Employer = user.employer” — to decide visibility. Because it keys off metadata, one rule protects millions of documents without per-document permissions.
Does DocuPro support single sign-on?
Yes. Users authenticate with Microsoft Entra ID SSO. Group membership then decides what each role can do in DocuPro.
If a user cannot see a document, can they still find it in search or a workflow queue?
No. The same rules apply to search results, workflow queues, printing, export, and the viewer. A document a user cannot see never appears anywhere in the application.
Is there an audit trail?
Every document keeps version history with the original retained, and annotations, stamps, and workflow stage changes are recorded against the document.