One publish action
The live page and latest API response update together.
Publish once. Stay consistent everywhere.
Terms updates that go live everywhere without the chaos.
Upload, publish, schedule, and roll back from one flow. Each version is immutable, every live route is explicit, and integrations stay aligned through consistent API responses and signed publish events.
admin/companies/northstar-health/tnc/customer-terms
Document control
Hosted URL, live version, and next draft in one workspace
Northstar reviews the public route, the latest effective version, and the next ready draft from one document view.
One source of truth
Current and historical versions stay explicit and reviewable.
One reliable sync path
Downstream systems subscribe to signed publish events with retries.
Single
latest-effective pointer
Per document, one canonical live version is always explicit.
SHA-256
artifact hashing
Source and generated HTML hashes are retained for provenance.
Signed
publish webhooks
HMAC-signed events with retry attempts and delivery logs.
Server-Gated
plan enforcement
Document/webhook/scheduling limits are enforced server-side.
What changes after launch
Fewer handoffs. Fewer mismatches. Faster updates.
The workflow removes the usual friction around policy changes and keeps every customer-facing surface aligned after publish.
Outcome 1
Stop version mismatch incidents
Customers, support, and internal teams stop seeing different Terms in different places.
- Latest hosted page and latest API resolve the same effective version
- Version permalinks stay stable for historical references
- Rollback restores a known published state without ambiguity
Outcome 2
Cut publish coordination time
Updates move from draft to live without waiting on manual release windows.
- Upload, review, publish, schedule, and rollback in one flow
- Conversion status keeps progress visible while content is processing
- Teams can ship urgent policy changes in a controlled way
Outcome 3
Keep integrations predictable
Integrations read stable endpoints and receive signed publish events they can trust.
- Company-scoped API keys enforce tenant isolation
- Signed webhooks with retry attempts and delivery logs
- Latest and version-detail endpoints stay stable for embedding
Product proof
The control surface is built for real publish operations.
Show buyers the workflow they are evaluating: document-level control, centralized webhook visibility, draft-to-publish T&C management, and multi-company workspace switching in one admin surface.
admin/companies/northstar-health/tnc
Centralized operations
Document inventory, webhooks, and deliveries stay visible together
Operations teams can verify what is live, which endpoints are active, and whether publish events were delivered without leaving the dashboard.
Core capabilities
The outcomes you can validate in week one.
Single live source
One latest-effective route keeps customer-facing Terms consistent across every channel.
Immutable history
Every upload creates a new version with retained source and HTML hashes.
Reliable distribution
Hosted pages, latest API responses, and version endpoints stay aligned by design.
Operational visibility
Publish events are signed, retried, and logged so downstream synchronization is observable.
Included in every workspace
- Latest-effective hosted route + version permalinks
- Immutable versions with source + HTML hash artifacts
- Signed publish webhooks with retry attempt tracking
- Server-enforced plan limits for protected actions
How it works
From upload to live Terms in three steps.
Step 1
Upload and convert
Each DOCX upload becomes a draft version with conversion status from pending to ready.
Step 2
Publish now or schedule
Go live immediately, set a future effective date, or roll back to a previously published version.
Step 3
Distribute to every touchpoint
Signed webhook events and latest endpoints keep products, support surfaces, and docs in sync.
Implementation details
Implementation proof for security and procurement reviews.
Hosted delivery
A single latest URL plus stable version permalinks keeps live policy routing unambiguous.
API access
Latest, versions-list, and version-detail endpoints provide predictable integration surfaces.
Security baseline
Sanitized HTML, hashed secrets, and tenant-scoped access controls are enforced server-side.
Admin controls
Upload, publish, schedule, and rollback workflows are centralized in one operational flow.
Pilot playbook
What a real rollout looks like in the first two weeks.
Day 1
Set up your live baseline
Create your workspace, configure the first document, and confirm your canonical hosted URL.
Day 2-3
Upload and validate a draft
Upload DOCX content, review sanitized output, and verify immutable artifact hashes.
Day 4-5
Publish and synchronize
Publish the latest version and confirm hosted + API outputs are version-consistent.
Week 2
Automate and harden
Enable signed webhooks, inspect delivery logs, and run a rollback drill for operational confidence.
FAQ
Answers to the questions most teams ask before rollout.
Can we keep one public Terms URL while still preserving historical versions?
Yes. Each document maintains a single latest-effective public URL while every upload remains available as an immutable historical version.
Can we schedule a future effective date for approved Terms?
Yes. Publishing supports immediate go-live and scheduled effective dates, with background jobs handling timed transitions.
How do our systems know when new Terms go live?
On publish or rollback, Docompli emits signed webhook events and keeps detailed delivery attempts for verification and troubleshooting.
What if our webhook endpoint is temporarily unavailable?
Deliveries are retried with exponential backoff, and each attempt is recorded with status code and response details.
How is content safety handled for uploaded DOCX files?
Generated HTML is sanitized before persistence and rendering, and source + HTML hashes are retained for provenance.
Can we quickly revert to a previously published version?
Yes. Rollback makes a prior published version the latest-effective version while preserving the full immutable history.
Ready to evaluate
Run your next Terms update through a controlled pilot.
Validate publish consistency, historical integrity, and integration reliability in one workspace before broader rollout.
- One latest-effective URL per document
- Immutable version history with hash provenance
- Version-consistent hosted pages and API responses
- Signed publish events with retryable delivery logs