Controlled secure document viewing workflow

Sensitive documents need more than a simple file preview. Contracts, financial reports, legal files, HR records, medical documents, engineering files, and internal business reports should be handled with clear rules for access, storage, viewing, download, printing, and retention.

For quick online viewing, Doconut.app can be useful. It opens 70+ extensions in the browser without installing anything — PDF, DOC, XLS, PPT, PSD, DWG, SVG and the rest — free and with no account, with the size ceiling set per format from 5 MB up to 25 MB.

It is a hosted site, so be clear what that means: your file reaches our servers, is rendered there, and is deleted when the viewing session ends. There is no access control, no audit trail and no retention setting, because there are no accounts for those things to attach to.

However, when sensitive documents are part of a business application or internal workflow, the main question is not only whether the file can be opened. The main question is whether the application can control the workflow.

For .NET teams that need document viewing inside their own application, Doconut Viewer is the product to evaluate. It is designed for ASP.NET and modern .NET applications, and covers viewing plus optional search, annotation and conversion. Controlled printing is part of the viewer itself rather than a separate purchase.

Online Viewing vs. Controlled Application Viewing

Online document viewers are convenient. They are useful when users need to open a file quickly from the browser.

Online viewing can be a good fit for:

Quick document preview
Non-sensitive files
Simple viewing tasks
Testing how a document opens in the browser
Avoiding local software installation
Opening different document formats from one place

Doconut.app fits this kind of use case because it provides a simple online viewing experience for many file types.

Controlled application viewing is different. It is used when the document is part of a larger business workflow and the application needs to manage permissions, storage, logs, and user actions.

Controlled viewing is usually better when:

Documents are confidential
Users must sign in before opening files
Access depends on roles or permissions
Files are stored in approved locations
Download or printing must be restricted
Document access should be logged
The application must keep users inside its workflow
Search, annotation, conversion, or controlled printing are required

For these scenarios, Doconut Viewer is the more relevant solution.

Why Sensitive Documents Need Clear Access Rules

Sensitive documents should not be available to every user in the same way. Different users may need different levels of access.

For example:

One user may be allowed to view a contract but not download it.
A manager may be allowed to print a document.
A reviewer may be allowed to add annotations.
An administrator may be allowed to convert or export a file.
A guest user may not be allowed to open the file at all.

These rules should be handled by the application. A document viewer should fit into that security model, not replace it.

A controlled document workflow should include:

Authentication
Role-based authorization
Document-level permissions
Storage rules
Download rules
Print rules
Audit logging when required
Temporary file and cache management

The viewer is only one part of the workflow. The full application determines how secure the document process is.

Keeping Documents Inside Your Own Infrastructure

For many organizations, sensitive documents should remain inside approved infrastructure.

According to the Doconut FAQ, the Doconut Viewer SDK is not a SaaS or hosted service: it is installed in the customer's own environment, makes no calls to Doconut servers, and files stay under the customer's control.

That applies to the SDK only. Doconut.app is the opposite arrangement — a hosted public site where the file does reach our servers — which is exactly why this article separates the two.

This is important for companies that want document viewing inside their own .NET applications without sending files to an external document viewing service.

Your application can decide:

Where documents are stored
Who can access them
How they are opened
Whether users can download or print
Whether actions are logged
How temporary files and cache are handled
How long generated files are retained

This gives development teams more control than a separate upload-and-view workflow.

Why Offline Viewing Is Not Always Enough

Offline PDF viewers can be useful in some situations. They may be required when there is no internet connection or when a user needs a specific desktop tool.

However, offline viewing can also create challenges for sensitive workflows.

When a user downloads a document to open it locally:

The file may remain on the device.
The file may be copied or forwarded.
The file may be printed outside the application.
Local backups may store extra copies.
The application may lose visibility into who opened the file.
Different users may have different viewer versions.
IT teams may need to manage installations and updates.

Offline viewing can feel safer because it does not depend on an online tool, but it can reduce application-level control if files leave the system.

For business workflows, controlled in-application viewing can be a better option because users can review documents without leaving the application context.

Using Doconut.app for Quick Online Viewing

Doconut.app is useful when users need a simple online document viewer.

It can help with:

Opening PDF files online
Previewing Word documents
Viewing spreadsheets
Opening presentation files
Previewing image files
Viewing CAD formats such as DWG
Avoiding desktop software for simple viewing tasks

Doconut.app is a good fit for quick preview needs, especially when the file is not part of a sensitive internal workflow.

For confidential documents, always review your organization’s security rules before uploading files to any online viewer.

Using Doconut Viewer SDK for Sensitive Workflows

For sensitive document workflows in .NET applications, Doconut Viewer is the main solution to consider.

Doconut Viewer helps developers display documents inside their own applications. It can be used in scenarios such as:

Internal business systems
Legal platforms
Document management systems
Insurance workflows
HR portals
Financial applications
Healthcare-related systems
Engineering document portals
SaaS products with uploaded documents

Doconut Viewer can be combined with optional plugins depending on your workflow. There are four, and controlled printing is not one of them:

Search Plugin
Annotation Plugin
Converter Plugin
DICOM Plugin — medical imaging, which is why .dcm and .ima are not on the free viewers

Controlled printing comes with the viewer. It is a capability of the base product, so restricting printing is a configuration and permissions question rather than a licensing one — worth knowing before you budget.

Search, Annotation, Conversion, and Printing

Sensitive workflows often require more than simple viewing.

Users may need to:

Search for text inside a document
Highlight or comment on a section
Add a stamp or mark a document for review
Convert a file to another format
Print only when allowed by policy
Keep the original file unchanged
Store workflow data separately from the document

Doconut covers these needs partly through plugins and partly in the base viewer.

The Search Plugin finds text inside supported documents. Note what that means for scanned material: it searches a text layer the document already carries. There is no OCR, so a page held only as an image has nothing to find.

The Annotation Plugin adds notes, highlights, drawings, stamps and other review marks.

The Converter Plugin handles document conversion inside .NET applications.

Controlled printing is built into the viewer, not licensed separately.

Your application should still decide who can use each feature and under which conditions.

Security Best Practices for Sensitive Document Viewing

When building a sensitive document viewing workflow, review these best practices:

Require users to sign in before accessing documents.
Check document permissions before opening a file.
Avoid public URLs for confidential documents.
Store files only in approved locations.
Decide whether download is allowed.
Decide whether printing is allowed.
Log document access when required.
Validate uploaded files on the server.
Review temporary file and cache behavior.
Review converted output storage if conversion is enabled.
Keep annotation data under application control.
Test with real user documents before deployment.
Review security and compliance requirements with your internal team.

These practices apply whether you use an online viewer, an offline viewer, or an embedded viewer SDK.

When to Use Doconut.app

Use Doconut.app when:

You need quick online document preview.
The file is not part of a controlled business workflow.
Users do not want to install desktop software.
You need to preview common formats from the browser.
The document is non-sensitive or approved for online viewing.

Doconut.app is useful for simple viewing tasks.

When to Use Doconut Viewer SDK

Use Doconut Viewer when:

You are building a .NET application.
Documents are sensitive or business-critical.
Users need to view documents inside your system.
Your application must control permissions.
You need search, annotation, conversion, or controlled printing.
Files should remain under your infrastructure rules.
You need documentation, demos, evaluation resources, and support.

Useful Doconut resources:

Key Takeaways

Sensitive documents need controlled access, storage, viewing, printing, and logging rules.
Offline viewing can be useful, but it may create local copies outside the application workflow.
Online viewing is convenient for quick preview tasks.
Doconut.app is useful for simple online document viewing.
Doconut Viewer SDK is better for controlled .NET workflows involving sensitive documents, because it runs in your environment and calls nothing external.
Doconut holds no ISO 27001, SOC 2 or HIPAA certification. The SDK's security argument is architectural — the file never leaves your boundary — and the surrounding controls remain yours to build and evidence.

Common Questions

Is offline viewing always safer for sensitive documents?
Not always. Offline viewing can reduce external upload risks, but it may create local copies outside the application workflow. Security depends on the full process, not only whether the viewer is online or offline.

Can I use Doconut.app for sensitive files?
Doconut.app can be useful for online viewing, but confidential files should only be uploaded if your organization allows that workflow. For controlled business workflows, review Doconut Viewer SDK.

Is Doconut Viewer SDK a hosted SaaS service?
No. According to the Doconut FAQ, Doconut is installed in the customer’s own environment and no calls are made to Doconut servers.

Can Doconut Viewer SDK support annotations?
Yes. Annotation workflows can be implemented with the Annotation Plugin.

Can printing be controlled?
Yes, and it does not require an extra plugin — controlled printing is part of the viewer. What decides who may print is your application's own permission rules.

Where can I evaluate Doconut Viewer SDK?
You can start with the official download page:

Download Doconut

Conclusion

Offline PDF viewers can be useful in some situations, especially when users need local access. However, offline viewing is not always enough for sensitive business workflows because files may leave the application’s control.

For quick online preview, Doconut.app is a practical option.

For .NET applications that need controlled document viewing, permissions, search, annotation, conversion, printing, and infrastructure-level control, Doconut Viewer SDK is the main product to evaluate.

To continue, review these Doconut resources:

Why Controlled Document Viewing Matters for Sensitive Work