Skip to content

Included in Better

Policy Profiles

Policy Profiles standardize how repeatable document jobs run across teams, batches, and compliance gates.

Problem

Sensitive PDFs can contain visible secrets, hidden data, active content, weak permissions, or signatures that need validation.

Use

Apply protection controls or inspect trust state, then retain evidence for the release decision.

Evidence plan

What this unlocks

  • Versioned, reusable pipeline-step presets executed via the pipeline runner
  • Run from the document workspace once signed in
  • Better package access keeps the path explicit
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
Searchable PDFField review notesClean source metadata
Complex pathForm W-9

Secure intake pipeline

Run a repeatable intake path that extracts fields, redacts sensitive identifiers, verifies removal, compresses the output, and records evidence.

  1. 1Upload the form batch
  2. 2OCR and extract fields
  3. 3Apply redaction policy
  4. 4Verify redaction
  5. 5Compress and export packet
  6. 6Attach audit trail
Redacted PDFStructured field exportRedaction verification report

Inputs & outputs

Accepted formats
pdf
Produced formats
pdf

Common use cases

  • Reuse approved processing settings
  • Control allowed pipeline steps
  • Apply consistent security and quality gates

Workflow steps

  1. 1Define the profile rules
  2. 2Attach the profile to a tool or pipeline run
  3. 3Review exceptions and saved output artifacts

Outputs

  • Protected or sanitized PDF
  • Verification report
  • Security audit entry

Review checks

  • Verify destructive changes
  • Separate secret delivery from artifact generation
  • Retain reports with the final version

API

Endpoint family: /v1/security, /v1/forensics, /v1/jobs
  • Reference policy profile IDs from headless pipeline runs.
  • Use profiles to keep automation aligned with package and workspace policy.
Integration overview

Limits

Availability
Included in Better
Readiness
beta
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

Public example workflows

Integration overview

Roles and use cases