Attaching documents to vehicles, damage cases, penalty notices, and receipts
This article explains how the same document tools attach files to different kinds of records — vehicles, damage cases, penalty notices, and receipts — and what is unique about each.
The same engine, different parents
Every attachment in MobilityManager flows through the shared DocumentModule. You always attach a file from inside a record, and the record supplies its association type and ID automatically. The upload, category, size, versioning, and permission rules are identical everywhere. What differs is which parent record the file is linked to and any parent-specific validation.
Supported record types
| Record | Association type | Typical use |
|---|---|---|
| Vehicle | Vehicle | Registration papers, contracts, and inspection certificates in the Fahrzeugakte (vehicle file). |
| Damage case | DamageCase | Photos of the damage and repair estimates. |
| Penalty notice | Mandate | Scans of the Strafmandat (penalty notice). |
| Receipt / expense | Beleg | The receipt or invoice behind a Beleg (receipt/expense document). |
| Driver's licence | driver-license | Licence images for Führerscheinkontrolle (driver's licence check). |
| Compliance report | license-compliance-report | Generated licence-compliance reports. |
Attach a file to any record
- Open the specific record — the vehicle, damage case, penalty notice, or Beleg.
- Open its documents area and choose the file.
- Pick a required category.
- Upload. The file is stored as version 1 and linked to that record.
You need the documents:manage permission to attach, and documents:view to see and open existing attachments.
Parent-specific validation
Because a file must belong to a real record, each area checks the parent before storing. For example, uploading a vehicle document to a vehicle that does not exist is rejected with "Vehicle not found." Similarly, Beleg, damage case, and penalty notice uploads fail if the parent record is missing. This keeps orphaned files from accumulating.
Note: You cannot attach a file to a record type the module does not recognize. Unsupported types return "Document operation unavailable", which is why attachments are always started from within a record rather than a standalone upload page.
Penalty notices can also ingest from a URL
Most record types accept direct file uploads. Penalty notices additionally support ingesting a document from an external URL: the platform downloads the file and stores it internally, recording its source as URL ingestion rather than a manual upload. The result is an ordinary document you can view and download like any other.
Tip: A cross-reference field lets you tag an attachment with a related Beleg reference. Use it to connect, say, a repair invoice on a damage case to the Beleg that pays it, so reviewers can trace the paperwork.
Related
- How documents work across the platform
- Uploading a document and file size limits
- Downloading a document
- Tenant scoping and document isolation
