Experlogix Documents provides a clear distinction between Production and Non-Production projects. This separation allows organizations to safely develop, test, and experiment with templates and forms without impacting business-critical production workflows or risking unintended live outputs, while allowing template previews and document executions to run without consuming DPUs (note that AI translations still consume DPUs).
Projects created before these classifications were introduced must be categorized by an administrator as Production or Non-Production prior to December 31, 2026. After that date, any remaining unclassified projects will automatically default to Non-Production.
Overview
When creating a new project (or classifying existing projects during the grace period), you can designate its environment stage:
|
Project Type |
Purpose |
Watermarking |
License Consumption |
|---|---|---|---|
|
Non-Production (Default) |
Testing, training, template design, and experimentation. |
All generated outputs (PDF documents, Word documents, and web forms) include a visible "Test" watermark. |
Document generation in non-production projects does not consume Document Processing Units (DPUs). AI translation within Content Manager still consumes DPUs. |
|
Production |
Live, business-critical operations. |
Clean outputs generated without test watermarks. |
Document executions consume standard DPUs according to your organization's license. |
Setting the Project Type (New Projects)
When creating a new project:
-
Navigate to the Projects page.
-
Select + Create Project.
-
In the project creation dialog, select the Project Type:
-
Non-Production (Selected by default)
-
Production
-
Complete the remaining project details and select Create.
Important:
-
The project type selection is mandatory upon creation.
-
Once a project is created, its classification is permanent and immutable. It cannot be modified through standard project settings.
Workaround:
If you need to change the project type after creation, export your project assets, create a new project with the desired classification, and import the assets into the new project.
What to Do with Existing Projects (Migration & Grace Period)
If your organization has projects created prior to this rollout, they undergo a structured transition period.
Initial State: Unclassified
-
All pre-existing projects are automatically migrated into an Unclassified state.
-
No Service Interruption: Unclassified projects continue to operate normally without functional restrictions during the transition period.
The Grace Period (Active until December 31, 2026)
During the grace period, organization and project administrators can review and classify existing projects.
-
Banner Notifications: Organization Administrators and Project Administrators will see a banner notification:
"The projects in this organization must be classified as Production or Non-Production before 31 December 2026." -
Highlighting & Filtering: The project list highlights unclassified projects and allows filtering by classification status.
-
Self-Service Classification:
-
Project Administrators can classify the individual projects they administer.
-
Organization Administrators can classify individual projects or perform bulk classification for multiple projects simultaneously.
-
How to Classify an Existing Project
-
Navigate to the Projects list.
-
Identify projects marked as Unclassified.
-
Select the project to open its details, or select the actions menu (...) next to the project name.
-
Select Classify Project.
-
Choose Production or Non-Production.
-
Select Confirm.
Once an unclassified project is classified by an administrator, the classification becomes permanent.
Workaround:
If you need to change the project type after creation, export your project assets, create a new project with the desired classification, and import the assets into the new project.
What Happens When the Grace Period Ends?
After December 31, 2026:
-
Any project that remains Unclassified will be automatically set to Non-Production by the system.
-
Once automatically set to Non-Production, all subsequent outputs generated by the project will carry the "Test" watermark.
-
The system records an audit trail event denoting that the classification was system-defaulted after the grace period.
Summary & Recommended Action Plan
|
Step |
Responsible Party |
Action |
Timeline |
|---|---|---|---|
|
Organization & Project Admins |
Review all active projects in your organization. |
Immediate |
|
Administrators |
Classify live/client-facing projects as Production and development/testing projects as Non-Production. |
Before Dec 31, 2026 |
|
System |
Any remaining unclassified projects automatically default to Non-Production. |
After Dec 31, 2026 |