Documentation Audit Report (February 2026)

This report summarises the findings of a comprehensive audit of all 139 pages in the ODSH Confluence documentation space, conducted in February 2026. Five specialist agents reviewed every page against the OptimiDoc Server codebase, verifying accuracy, completeness, formatting, and consistency. The audit identified 6 new pages to create, 2 critical accuracy issues, 5 moderate issues, and 25+ minor issues across the documentation.

Audit Scope

Summary by Section

Critical Issues (4)

These require immediate correction as they contain factually incorrect information.

CRIT-1: Rules — Conditions and Actions Reference (42762374)

The "Available In" column for nearly every condition and action is inaccurate when compared to RuleContext.cs. Many conditions and actions are listed as available in contexts where the code does not support them. For example:

• "Force Black & White" is listed as available in Accept Job, Before Print, and Release Job — but the code only supports it in Before Print

• "Job Type" is listed as available in Accept Job and Before Print — but the code only supports it in Release Job

• "Number of Pages" is listed in Accept Job, Before Print, and Release Job — but code only supports Release Job

Action: Rebuild the entire conditions/actions table from RuleContext.cs:AvailableConditions() and AvailableActions() methods.

CRIT-2: Rules — Rule Contexts Reference (42991693)

Same issue as CRIT-1 — per-context condition and action tables list many items that the code does not make available in those contexts. Additionally, the page states "conditions are the same as Accept Job" for Before Print, which is incorrect (they differ significantly in code). Also contradicts the Rules Hub on whether "first match wins" or "all matching rules execute".

Action: Rewrite all four context tables from the code. Clarify rule chaining behaviour.

CRIT-3: Supported Devices — Hub page (42533051) and 5 missing vendor pages

The hub page only lists 5 of 10+ supported vendor types. Five vendors with full codebase implementations have no documentation pages:

• Canon — custom REST API, Gen2/Gen3 distinction, full web terminal

• Kyocera — REST API on port 8080, native scan support, full web terminal

• Ricoh — SOP REST API, landing page only (no full web terminal)

• Develop — OEM of Konica Minolta, identical OpenAPI platform

• Fiery — print-only target, no embedded terminal

Additionally, HP Pro is a distinct vendor type (HewlettPackardPro) with different capabilities from HP Enterprise but is not documented separately.

Action: Create 5 new vendor pages and update the hub table. Either create a separate HP Pro page or add a subsection to the existing HP page.

CRIT-4: Scanning — SharePoint List Parameter page (42253818) is missing

The page returns 404. The Scan Parameters Reference hub links to this page ID. The SharepointList parameter type exists in the codebase with fields: Url, Web, Path, Login, Password, Domain, ValueField, DisplayField, RefreshPeriod.

Action: Recreate the SharePoint List Parameter page under Scan Parameters Reference (42860564).

Moderate Issues (3)

MOD-1: Driverless Print (42729577) — IPP format discrepancy

The page lists application/pdf, application/postscript, image/jpeg as supported document formats, but SpoolerController.cs defaults show application/octet-stream, application/postscript, text/plain, application/vnd.hp-PCL. The page describes configurable attributes from default.ipp, not the hardcoded defaults. A clarifying note is needed.

Action: Add a note explaining that the listed formats are configurable defaults from default.ipp and may differ from built-in defaults.

MOD-2: Diagnostics — Cluster Nodes (43319316) has no React UI page

The page is fully documented but there is no corresponding React UI page in optimidoc-ui/src/pages/diagnostics/. This may be a legacy MVC feature not yet migrated to React, or a planned feature.

Action: Verify whether this is a legacy feature. If so, add a note that it is accessed via the legacy interface. If planned, mark as "Coming Soon".

MOD-3: GDPR Compliance (43024442) — Export User Data feature not implemented

The page describes an "Export User Data" button on the user profile page, but this feature does not exist in the current React UI code.

Action: Remove the Export User Data reference or mark it as a planned feature.

Minor Issues (38)

Vendor Documentation — Authentication Methods Incomplete (5 pages)

All 5 existing vendor pages (Konica Minolta, Xerox, HP, Lexmark, Epson) list only basic auth methods (Card, PIN, username/password) but omit SSO, External Authentication, and Card+PIN combinations where the code supports them.

Vendor Documentation — Missing Features (5 pages)

Screenshot Placeholders (across all sections)

27 pages have leftover > _Screenshot: ..._ placeholder text that should be removed or replaced with actual screenshots:

Other Minor Issues

New Pages to Create (6)

Recommended Update Priority

Phase 1 — Critical Fixes (immediate)

1. Rewrite Rules Conditions and Actions Reference (42762374) from code

2. Rewrite Rule Contexts Reference (42991693) from code

3. Create Canon, Kyocera, Ricoh vendor pages

4. Recreate SharePoint List Parameter page

5. Update Supported Devices hub table

Phase 2 — Moderate Fixes (short-term)

1. Add IPP format clarification note

2. Verify Cluster Nodes page against legacy UI

3. Remove or flag GDPR Export User Data reference

4. Create Develop and Fiery vendor pages

Phase 3 — Minor Fixes (ongoing)

1. Update auth method tables on all 5 existing vendor pages

2. Add missing vendor features documentation

3. Remove leftover screenshot placeholder text (27 pages)

4. Fix Appearance and Skin logo dimensions

5. Correct Quota Overlap Strategies additive description

6. Expand media size list in Input Options

7. Address other minor issues

Positive Findings

• All 139 pages have substantive, professional content — no placeholder-only pages remain

• British English is used consistently across the entire space (organisation, colour, licence, centralised, etc.)

• ODSH formatting style is consistent (bold intro paragraph, --- dividers, ## **Bold H2**, tables with bold headers)

• No AI feature mentions — documentation correctly focuses on OptimiDoc Server (on-premise) only

• Cross-linking between pages is thorough and uses correct page IDs

• Product Overview, Getting Started, Dashboard, Reports, and Support KB sections (47 pages) are all production-ready with zero issues

• Quota documentation is exceptionally accurate — feature tables, overlap strategies, and transaction types match the codebase precisely

• Users, Settings, and Diagnostics sections show remarkably high code-to-doc accuracy across all field names, UI elements, and workflows