Downloading a document
This article shows you how to find and download a file that was attached to a record in MobilityManager, and what the platform returns when you open one.
Before you start
Downloading and previewing require the documents:view permission, typically held by FleetManager and SystemAdmin. You also need an active company (tenant) in your session; without one, document requests stop with "Tenant context is required for document operations."
Find the document
- Open the record the file is attached to — for example a vehicle, a Beleg (receipt/expense document), a damage case, or a Strafmandat (penalty notice).
- Open that record's documents area. The platform lists the attachments for that record, newest first.
Each entry in the list shows the file name, content type, size, category, upload date, and who uploaded it. Use these details to pick the right file before downloading.
Download or preview
Select the document you want. The platform streams the file back to you with its original file name and content type, so it opens or saves exactly as it was uploaded. If a file was uploaded without a detectable content type, it is served as a generic binary download.
Note: Downloads always return the latest version of a document. If the file was replaced after its first upload, you receive the most recent version, not the original.
What you might see instead of a file
| Situation | Result |
|---|---|
| The document ID does not exist for that record | "Document not found." |
| The stored file content is missing from storage | A not-found response indicating the content is unavailable. |
| You lack permission for that document's area | An access-denied response (HTTP 403) that does not reveal whether the file exists. |
| Storage could not be reached | A retrieval-failed message; try again shortly. |
The access-denied response is deliberately generic. It tells you that you cannot view the document without confirming or denying that a particular file is present, which prevents probing.
Encrypted files download as normal files
When encryption at rest is enabled, files are decrypted on the way out automatically. You never handle keys or ciphertext — the download is the original, readable file. Files uploaded before encryption was enabled still download correctly, because the platform detects whether a stored payload is encrypted.
Export artifacts
Some files are generated by the platform rather than uploaded by you — for example expense export spreadsheets. These export artifacts are retrieved by their document ID and are kept separate from the ordinary attachment lists, so you will not see them mixed in with a record's uploaded documents.
Tip: If a colleague cannot open a file you can, check their role. Download is gated by documents:view, and some custom roles are granted upload rights without view rights or vice versa.
Related
- Uploading a document and file size limits
- How documents work across the platform
- Deleting a document
- Tenant scoping and document isolation
