Media registers files, their properties and storage settings, then connects them to the records they support.
The contract, the site photo, the signed form — on this platform each lives with what it concerns: attached to the record, stored in your deployment, findable from both directions. This manual covers the media registration, its storage, and its wiring.
What you record
The media registration
| Field group | What it holds |
|---|---|
| Identity | Name, description, the original filename |
| Type | The media type (image, video, document, file — your types) |
| The file | The storage key, the format, the size in bytes, the checksum |
| Dimensions | Width, height, duration, page count — the properties per type |
| Storage | The storage policy (which of your storage definitions this file lives under), where it lives in your deployment |
| Lifecycle | The status, the public flag, who uploaded and when |
| Enrichment | The thumbnails, the metadata, the categories and features (the characteristic stack, as everywhere) |
The storage policy is yours: the files live under the storage definitions your operation configured — your deployment, your capacity, your backups. Nothing about your documents lives in a vendor's storage by default.
The thumbnails are generated: previews for the lists and galleries, computed by the platform, held on the registration.
What you can do
- Upload — the file lands under your storage policy, with its metadata held
- List, search, filter — by type, category, uploader, status; bulk actions
- Attach to anything — the wiring below; a file can live with a work, a person, a content entry, a venue
- Manage versions of truth — the checksum and metadata make each file identifiable, not just findable
- Relate — the wiring below
What it connects to
| Target | Examples |
|---|---|
| Works | The proposal attached to the work it answers |
| Content | The images an entry carries |
| Employees & accounts | The CV, the ID scan, the certifications |
| Venues | The site photos, the floor plans |
| Events | The meeting recordings and materials |
Where it feeds
Attached media is evidence with provenance: the inspection photo attached to the record it evidences, the certificate attached to the account it authorises. The readings that reach for proof find it wired to the story — the media platform story is the buyer page; this manual is the attachment surface.
The pattern note: same four-part structure — record, do, connect, feed. The media manual is where the attachment pattern shows: a file that names its subject is evidence; a file in a drive is an orphan.
Implementers connect your storage definitions at adoption — capacity, backup posture, access rules; the files land where you decided.
No record is an island
Every file relates to the record it evidences, the person who uploaded it, the work it documents. The attachment layer is the relationship layer holding what words alone cannot — and the wiring keeps the proof with the story.
Review the record and its context before deciding what to do next.
Content → · Venues → · All manuals → · The Media platform page →
Check your work
Before uploading a certificate or site image, confirm the intended audience, storage policy and record assignment. Check the actual file and preview after upload. A checksum identifies file content; it does not verify the truth of a document or confer permission to share it.
Available screens and actions depend on your deployment and permissions. Use this manual alongside the configured workflow and the capability demonstration for your installation.