Overview
Ottili Files is the shared file and storage foundation of Ottili ONE. Instead of every product maintaining its own isolated uploads, all modules share the same company-scoped storage layer. A file attached to a quote in Business Hub is exactly the same file that Ottili AI reads for context or that a Flow processes as a workflow step.
This article explains how Files is used across products, the role each product plays, and the rules — tenant isolation and permissions — that apply consistently everywhere.
One storage layer for every module
Ottili Files is not an isolated upload widget. Files live in a shared, company-scoped store that the modules access through the same platform mechanisms. That delivers three concrete benefits:
- No duplication*: the same source file is not re-uploaded per product.
- End-to-end context*: what is produced in one module is immediately available in another.
- Unified control*: access and permissions follow the same model across all products.
Cross-product usage
Ottili AI
Ottili AI reads files for context (for example briefings, spreadsheets or contracts) and can generate new files — summaries, drafts or images. Generated files remain owned by the company and land in the same storage layer.
Business Hub
In Business Hub, files are attached to business objects: quotes, orders, invoices and customer records. An attachment is linked directly to its record and inherits its permissions — anyone who cannot see the record cannot see the attachment either.
Ottili Flows
Flows read, move, transform and generate files as workflow steps. Recurring file tasks can be automated this way without crossing system boundaries.
Ottili LD3
LD3 uses source and media files as inputs for topics, facts and publishing jobs. A source uploaded once can be reused across multiple content pipelines.
Ottili Cloud
Ottili Cloud provides the underlying storage and infrastructure for Files. Ottili Cloud is currently in an early-access (pre-release) state; the file layer itself is part of the generally available platform.
Ottili Coder
In Ottili Coder, files can be attached to missions so the agent has context or can drop artifacts.
Status at a glance
| Product | Role for Files | Status |
|---|---|---|
| Ottili Files (core) | Shared storage foundation | Available (GA) |
| Ottili AI | Reads and generates files | Available |
| Business Hub | Links files to records | Available |
| Ottili Flows | Automates file steps | Available |
| Ottili LD3 | Uses source / media files | Available |
| Ottili Cloud | Storage infrastructure | Early Access (Pre-Release) |
| Ottili Coder | Files on missions | Available |
Status labels follow the product and feature status registry. For the exact meaning of Available, Beta, Early Access, Planned and Concept, see [Understanding feature status labels](/docs/understand-feature-status-labels).
Security and tenant isolation
Every file belongs to exactly one company. Access follows the same tenant boundary as the rest of Ottili ONE — files never leak across companies. Permissions are driven by roles and entitlements and apply consistently across every module. So an attachment in Business Hub is visible exactly when its record is visible, because Files, Business Hub and the other modules share the same permission model. See [Shared permissions and entitlements](/docs/shared-permissions-and-entitlements) for details.
Related articles
- [Ottili Files](/docs/ottili-files)
- [Business Hub overview](/docs/business-hub-overview)
- [Ottili AI](/docs/ottili-ai)
- [Ottili Flows](/docs/ottili-flows)
- [LD3 Content](/docs/ld3-content)
- [Workspace and modules](/docs/workspace-and-modules)
Was this article helpful?
