Features
From draft to the published version.
TermShelf covers the entire workflow for legally relevant website documents — from structured maintenance through review and approval to targeted publishing and live verification.
Workflow overview
Seven steps that fit together.
- 1
Set up structure
- 2
Maintain documents
- 3
Define variants
- 4
Start review
- 5
Trigger publishing
- 6
Check live drift
- 7
Triage findings
- 1
Set up structure
- 2
Maintain documents
- 3
Define variants
- 4
Start review
- 5
Trigger publishing
- 6
Check live drift
- 7
Triage findings
A
Workspace & structure
The target structure defines where a legal text applies — for a specific website, language, region, or commercial variant.
- Workspaces
- Brands
- Products
- Sites
- Domains
- Locales
- Markets
- Site profiles
B
Documents & structured content
Legal texts are not managed as loose HTML blocks but as structured documents with sections and validated content blocks.
- No free HTML paste
- Sections and typed blocks
- Stable keys
- Document types
- Search and filter
C
Variants & overrides
Variants enable targeted deviations without copying entire documents.
- Base document
- Locale, market, profile variants
- Replace or suppress inherited blocks
- No duplicated full texts
D
Versioning & history
Every approved version remains traceable. Restorations create new drafts rather than overwriting history.
- Immutable snapshots
- Version numbers
- Diffs between versions
- Restoration as a new draft
- History is never modified
E
Review & approval
Approvals are not hidden in informal chats or emails but mapped as an auditable workflow.
- Single reviewer
- Sequential review
- Threshold approval
- Self-review not allowed
- Decisions and notes
F
Publishing
Publishing happens with target precision for specific sites, languages, markets, or profiles.
- Target-aware publication
- Asynchronous publishing
- Published artifacts
- Rollback via controlled pipeline
G
Delivery
Websites and apps consume published content via a fast, read-only delivery interface.
- Public Delivery API
- JSON delivery
- HTML fragments
- ETags and cache headers
- Version pinning
H
Scanner & findings
Live drift detection reveals whether the approved version is actually visible on the website.
- Crawl of public customer sites
- Comparison with approved version
- Drift detection
- Open and triage findings
I
AI-assisted change suggestions
AI-assisted suggestions can prepare possible updates. Changes are never applied or published automatically.
- Suggestions as recommendations
- Adoption is decided by users
- No automatic adoption
- Not a substitute for legal advice
- Legal review recommended
J
Webhooks & integration
Publication and lifecycle events are integration-ready.
- Publication events
- Signed webhooks
- Replayable deliveries
- Integration with external systems
K
Audit & operations
Operational events and audit data remain traceable — failed jobs can be retried under control.
- Workspace event stream
- Audit logs
- Retry for failed jobs in the customer app
- No hidden mutation of history
Note on AI-assisted change suggestions
- Suggestions are non-binding recommendations.
- Changes are never automatically adopted or published.
- Acceptance, adjustment, or rejection is decided solely by users.
- Legal review by qualified counsel is recommended.
- TermShelf is not a substitute for legal advice.
Start the workflow in TermShelf
Manage and publish legal content with full control.
TermShelf brings privacy, legal notice, terms, and other website documents into a structured workflow.