Understand generated document storage names
Know that the original filename and generated stored name are separated.
Exact navigationTechnical storage → module uploads/{application_id}
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide covers
Know that the original filename and generated stored name are separated. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Upload a controlled file.
- Verify the display uses the original name/type while storage uses the generated name.
Fields, choices and supported possibilities
Stored filenameGenerated MD5-style unique name
Folder mode0755
File mode0644
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-admin-documents/
Code-backed validations and workflow rules
- The supplied upload and download controller applies this behaviour.
Expected result and verification
- Understand generated document storage names completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.