Setting Up DCMS for the First Time
How to configure the Document Control Management System before creating and publishing documents.
DCMS manages controlled documents like policies, standards and procedures through their whole lifecycle, from creation through approval, publishing, periodic review and retirement. Before anyone can create a document, a DCMS Manager has to configure how documents are organized, who reviews them and where published documents are stored.
The setup itself goes quickly. The decisions behind it take more thought. How you structure document types, reviewer roles and categories affects how every document moves through approval and how easily you can find it later, including in front of an auditor. Settle on a structure first, then configure.
You can change any of these settings later. It's still best to start small, test one document all the way through, and expand once the workflow fits your process.
⚠️Prerequisites: Users must have the DCMS Manager entitlement to access the Reviewer Configurations.
Recommended starter configuration:
-
Categories: IT, HR, Operations, Legal
-
Reviewer Types: Owner, Manager, Executive
-
Document Types: Policy, Standard, Guideline, Procedure
-
Repository: Use the default repository already in place.
Set Up Categories and Subcategories
-
Navigate to the Categories section in DCMS settings.
-
Categories represent how documents are grouped across your organization — typically by department.
-
Subcategories represent key processes within each department.
💡Start with 3–5 categories. Examples: IT, HR, Finance. Subcategories might include Access Control or Code of Conduct under the appropriate department.


Configuring Reviewer Types
Reviewer types define which roles review documents and which users can review in each role. Setting them up has two parts: creating the reviewer types on the Reviewer Configuration tab, then assigning users to them through each user's entitlements. Users can belong to more than one reviewer type, so nobody needs a duplicate account.
For step-by-step instructions, see How to Configure DCMS Reviewer Types.
Set Up Document Types
-
Navigate to List Types.
-
Document Types determine how documents are categorized and how users create them. Add additional types only after you've validated the basic workflow.
💡Recommended starting types: Policy, Procedure, and Standard.
When configuring each document type, you'll also need to assign default approvers and reviewers. These defaults determine who is automatically included in the approval workflow when a document of that type is created.

💡Add additional document types only after you've validated the basic workflow.
Configure the Repository
A repository is required for attachments, imported documents and for documents to be published. Without one, documents can be created and submitted but cannot reach Published status.
💡Use the default repository during initial setup.

Create and Publish Your First Document
Once the configuration is complete, the best way to validate your setup is to take one document through the full cycle before expanding further.
These guides can help you with the next steps.
-
Creating a New Document — how to create a document, complete the required fields, assign reviewers, and submit for approval.
-
Document Approval and Publishing — how approvers review, approve, and publish a document once it's been submitted.
Validating Your Setup
Before expanding your configuration, confirm your first document completes the full cycle: Create → Submit → Approve → Publish.
If something doesn't work, check the following: reviewer types are configured, a repository is set up, all required fields are completed, and approvers are assigned. Adjust and retry this is a normal part of the process.
Best Practices
Keep your initial setup minimal. Use the starter configuration recommended above and resist the urge to mirror every real-world workflow up front. Build one successful document cycle before adding complexity additional categories, reviewer types, and document types are much easier to configure once you've seen the system working end to end.
💡 A Note Before You Expand
You don't need a perfect system to get started. A working system, even a simple one, creates clarity. From there, you can refine and expand your configuration with confidence.