Content delivery scenarios
CDN public assets · private document review
CDN folder · tenant acme-ops · public static zone
Upload to CDN
marketing/product-brochure-2026.pdf
brand/logo-primary.svg
webapp/styles/portal-v3.css
replicating → CDN nodes (EU · US · APAC)
non-sensitive · versioned filename · ~1 min propagation
Unified content layer
“Private work, controlled sharing, and public delivery — without mixing them up.”
Platform
Documents, Files, and Content Distribution
Document-heavy steps belong inside live workflows—OCR, review links, and controlled file access in ProcessFlow and AI, not a separate document-AI pipeline beside ops.
Adoption context
- You need this when
- Document-heavy steps—OCR, review links, controlled file access—belong inside workflows, not a separate document-AI stack.
- Often bundled with
- Process Automation for live workflows on one platform.
- Not required if
- Your pilot workflow does not ingest files or distribute controlled review links yet.
Related workflow: Supplier evidence workflow · Adoption path
Content is not scattered across drives, email, and ad hoc storage—it lives in account-isolated storage, connected to workflows and WebApps.
Teams typically juggle file shares for internal documents, a separate CDN for public assets, manual email attachments for external delivery, and no link between files and the workflows that produce or consume them.
Tealfabric treats files as first-class platform objects—stored safely per account, reachable from automation, and deliverable to users and partners with the right access model for each scenario.
- One unified content layer—Documents, platform files, CDN, and public docs on your account
- Private work, controlled sharing, and public delivery—without mixing access models
- Browse, upload, preview, organize, and trash in the Documents workspace
- Secure review links with annotations, comments, status tracking, and review history
- CDN for intentionally public static assets; public docs for rule-controlled external handoff
- Workflow read and write, WebApp uploads, file connectors, and OCR from stored files
- Signed links with expiry, download limits, and download tracking
- Account isolation, upload validation, trash recovery, and workspace editor backups
Production patterns
From contract review to CDN brochures—one content layer behind each.
Two delivery models
Public CDN assets and private document review—on one platform.
Marketing uploads a brochure to the CDN folder for global WebApp and email delivery. Legal uploads a vendor contract to the private workspace, creates a review with secure links, and tracks external counsel annotations through resolution.
Content delivery scenarios
CDN public assets · private document review
CDN folder · tenant acme-ops · public static zone
Upload to CDN
marketing/product-brochure-2026.pdf
brand/logo-primary.svg
webapp/styles/portal-v3.css
replicating → CDN nodes (EU · US · APAC)
non-sensitive · versioned filename · ~1 min propagation
03 · Capabilities
Store, review, automate, and deliver—with the right access model per zone.
Files are inputs and outputs of automation—not an afterthought disconnected from ProcessFlow, WebApps, and connectors.
Day-to-day files, workflow outputs, and uploads—for signed-in users and automation. Preview PDF, images, text, and code formats in the browser; large files stream efficiently.
browse · upload
preview · trash
recoverable delete
Browse, upload, preview, organize, and recoverable trash in the Documents workspace.
Storage zones
Workspace, platform files, controlled external handoff, and CDN delivery—each zone has a clear purpose and access model.
Workspace documents
Day-to-day files, workflow outputs, uploads
Signed-in users and automation
Platform files
Assets tied to a specific platform record
Account-scoped, platform-organized
Public docs
Externally deliverable files (reports, invoices)
Rule-controlled gateway
CDN
Public static assets (images, CSS, brochures)
Open CDN URLs — non-sensitive only
Review and delivery lifecycle
Move from private draft to external review and controlled delivery without losing history.
Secure review links
Time-limited links—no platform account required
In-app viewing
PDF and document viewing with anchored feedback
Annotations and comments
Highlights, inline notes, threaded discussion
Review lifecycle
Pending → in review → commented → resolved
Review history
History of actions per review
Content delivery scenarios
CDN public assets · private document review
CDN folder · tenant acme-ops · public static zone
Upload to CDN
marketing/product-brochure-2026.pdf
brand/logo-primary.svg
webapp/styles/portal-v3.css
replicating → CDN nodes (EU · US · APAC)
non-sensitive · versioned filename · ~1 min propagation
How content gets in and out
Documents UI
Manual upload and management
connected
WebApp uploads
Customer forms and portals—multipart or chunked large files
connected
Workflow steps
Read, write, copy, and organize files in controlled automation
connected
File connectors
CSV, Excel, PDF, Word, JSON, XML, ZIP, OCR, and more
connected
Document viewer WebApp
External reviewers via secure links
connected
Documents API
Programmatic browse, upload, move, delete
connected
Fits the platform
Documents are where work lives. ProcessFlow moves and transforms files. WebApps handle upload intake and document viewer experiences. Datapools store structured data extracted from files. CDN delivers public static assets; public docs control external handoff.
One content layer for every audience
See Documents, CDN, public docs, and review workflows in action.
We walk through workspace management, secure review links, workflow file automation, CDN publishing, and signed download delivery—on the same platform as your workflows and connections.
Pilots start with one live workflow—system connections, steps, and full history.