File storage
Purpose
Files belong where the work they relate to lives. The store is therefore part of the system rather than a drive alongside it.
Two properties separate it from a network drive, and both are the reason it exists: every file is versioned — a new edition replaces the content without destroying the old one. And every file carries an explicit decision about whether customers may see it.
Scope
- Folders as the ordering device, plus an unfiltered overall view.
- A version history per file with a comment on the change. The file name stays, the content is
superseded.
- Per-file portal release, not released by default. Release is a decision, not an oversight.
- A marker for sensitive files, which are treated separately.
- Separate permissions for viewing, uploading and administering.
- An interchangeable storage location. Where the bytes physically live is an operational
decision — moving from local storage to object storage changes nothing about the handling.
Interplay
The working surface is Documents. Released files appear in the customer portal; generated documents from the commerce core and attachments from communication also land here.
Limits
- Portal visibility is two-stage. A portal right on the customer is not enough; the file
additionally needs its own release.
- The size limit comes from the installation, not from the application.
- A generated document is a document, not a window. It does not change when the template changes
later.
- Whether a file's full text is searchable depends on the setup — the file name always is, see