Reference & Data Model
Volume (volume)
A volume is the root of a file tree and belongs to a drive, a project, a person or the object whose attachments it holds.
Purpose
Section titled “Purpose”The volume defines who owns a file tree and what it looks like. It is a pure management object: it never appears as a row in the tree itself but is the place where the top-level folders and files live. Per owner there is at most one volume per kind („Dateien“ (Files), „Anhänge“ (Attachments)). (Data type: file data, system)
Where in the app
Section titled “Where in the app”- Shared drives (e.g. „Firma“): Projekt & Portfolio › Drive – Guides › Drive (global)
- Project: tab „Drive“ (the project’s „Dateien“ volume) – Guides › Drive
- Personal: every person’s „Meine Dateien“ (My files)
- The „Anhänge“ volume has no user interface; its files only appear in the „Dateien“ section of the respective object.
Fields
Section titled “Fields”No field of the volume is directly editable. Only its name is visible, as the root of the folder tree.
| Field | Technical | Type | Required | Meaning | Notes |
|---|---|---|---|---|---|
| Name | name |
Text | yes | drive title, project title, „Meine Dateien“ or „Anhänge“ | System |
| Owner kind | owner_kind |
Selection | yes | drive, project, user, issue, task or key_takeaway |
System |
| Owner | owner_<kind>_id |
Reference | yes | exactly one column per owner kind, e.g. owner_drive_id, owner_user_id |
System |
| Kind | slug |
Selection | yes | files (visible Drive) or attachments (attachments) |
System |
| Flat | flat |
Yes/No | yes | true: no folders allowed (attachments volume) |
System |
Relations
Section titled “Relations”| Related to | Kind | Required | On archive | On delete |
|---|---|---|---|---|
| Folder | has many | – | – | deleted along |
| File | has many | – | – | deleted along |
Rules & automation
Section titled “Rules & automation”- Created by the server only. The server creates the volume itself: shortly after a project, shared drive or user is created; a project Drive also on the first write by a workflow or Polaris (project Drive with the project title as name, „Meine Dateien“ for one’s own volume). An object’s attachments volume (issue, task, decision, takeaway) is created with its first attachment; attachments of a chat, a documentation or a technical structure land in the uploading person’s personal attachments volume. Clients may neither create nor modify volumes (“volumes are server-managed”).
- Separate worlds. Every volume is independent; a drive does not collect project files. Folders and files cannot be moved between volumes.
- Uniqueness: exactly one living volume per organization, owner and kind.