Skip to main content

Introduction

This section covers day-to-day usage of Docwize: uploading and managing documents, searching, completing workflows, and collaborating with your team.

If you're looking to configure Docwize — set up custom fields, permissions, workflows, templates, or system settings — see the Configuration section instead.

What Docwize enables users to do​

Docwize offers a robust and flexible toolkit for managing, analyzing, and sharing large volumes of documents and data efficiently. It is a comprehensive document, data and process management system designed for storing, managing, tracking, and reporting on documents, drawings, and workflows. It turns physical or electronic documents into strategic assets.

Two colleagues reviewing the Docwize platform together

The many modules in the Docwize ecosystem enable users to:

bulletLoad, import and integrate terabytes of documents and data
bullet Search across a repository of documents and data
bulletAutomate workflows
bulletUse semantic searching, clustering & AI Chat
bulletCreate and customize templates & forms
bulletAccess data through dataviews , lists & virtual folders

Different users, different paths​

Your path through Docwize can vary significantly depending on your role, permissions, and current task. A document controller, engineer, reviewer, approver, or administrator-supported user may each spend most of their time in different parts of the platform.

Depending on the task, you may work primarily in the Inbox, Explorer, Search, Records, dashboards, review tools, uploads, or document-level dialogs such as Document Details.

Typical user journey​

A common journey through Docwize looks something like this:

  1. Sign in to the portal.
  2. Open the Homepage or go directly to the area relevant to the task, using the sidebar.
  3. Continue work in the part of Docwize that matches your role and immediate need — for example the Inbox for workflow actions, Explorer for browsing documents, Search for finding information, or Records for structured data capture.
  4. Use document-level views such as Document Details when reviewing files, metadata, revisions, or relationships is relevant to the task.
  5. Move between modules as needed, depending on permissions, workflow design, and the type of work being done.