Skip to content

Enterprise control

Layer Policy Diff

Layer Policy Diff helps teams compare ocg/layer behavior for view, print, and export as part of a controlled DocuZeus workflow.

Request accessContact supportView capability
ToolboxBrowse the capability directoryWorkflowBrowse pathsAPIRoutes, scopes, and recipesProofInspect evidence

Problem

Teams need to know whether a PDF is standards-ready, suspicious, malformed, or safe to archive before they mutate it.

Use

Run read-only inspections and standards checks that return findings, verdicts, and exportable evidence.

Evidence plan

What this unlocks

  • Compare OCG/layer behavior for view, print, and export
  • Inspect without modifying the source document
  • Best package access keeps the path explicit

Workflow

Explore the workflow
Simple pathForm W-9

Quick OCR and field check

Turn a scanned form into a searchable PDF and verify the obvious fields before routing it.

  1. 1Upload the W-9
  2. 2Run OCR
  3. 3Inspect detected text and form regions
  4. 4Save a searchable copy

Tool chain

OCRForms Ops StudioSet Metadata Studio
Searchable PDFField review notesClean source metadata
Explore the workflow

Inputs & outputs

Accepted formats
pdf
Produced formats
report

Common use cases

  • Run PDF/A or PDF/UA preflight
  • Investigate suspicious hidden content
  • Export audit-ready evidence

Workflow steps

  1. 1Select the document or comparison set
  2. 2Run the read-only inspection or standards check
  3. 3Review findings and export the report or evidence bundle

Outputs

  • Findings report
  • Risk or standards verdict
  • Evidence bundle

Review checks

  • Group findings by severity
  • Route failures into remediation tools
  • Attach reports to audit or review records

API

Endpoint family: /v1/forensics, /v1/preflight, /v1/reports
POST/v1/documents/uploadPOST/v1/ocr/{document_id}GET/v1/jobs/{job_id}/downloadGET/v1/forensics/{document_id}/standards-preflightPOST/v1/forensics/{document_id}GET/v1/forensics/{document_id}/evidence-bundle
  • Forensics and validation tools typically return reports and findings instead of mutating source files.
  • Use /v1/forensics and related report endpoints for headless evidence collection.
Integration overview

Limits

Availability
Enterprise control
Readiness
private preview
Automation
Single-document workflow

Confirm entitlement, input requirements, and deployment fit in the package and API documentation before you automate this capability.

Integration overview

Evidence

Browse proof
Evidence is published with the related workflow and proof artifact when it is available for this capability.

Public example workflows

Integration overview
Simple

Quick OCR and field check

Form W-9

Turn a scanned form into a searchable PDF and verify the obvious fields before routing it.

Proof artifacts

Searchable PDF, Field review notes

Complex

Compliance evidence pack

NIST Cybersecurity Framework 2.0

Preflight a standards PDF, inspect hidden structure, validate trust signals, route findings, and export an evidence bundle.

Proof artifacts

Preflight report, Trust verdict

Roles and use cases

Governance and compliance teams

Compliance / Audit

Validate standards, signatures, audit trails, and retention posture.

Connected tools

Standards Preflight, Trust Chain Validation, Retention + Redaction

Preflight report: Standards preflight reportVerification result: Trust-chain verdict

Security teams

Security / IT

Control self-hosted processing, active content, and data paths.

Connected tools

Sanitize, JavaScript Control, Codec Policy

Review report: X-ray reportGenerated artifact: Parser diff scan

Legal and review teams

Legal Ops

Prepare evidence-ready PDFs and review packages.

Connected tools

Compare PDFs, Signature Center, Redact & Remove

Decision history: Compare review decisionsAudit record: Provenance ledger