Understand generated document storage names
This guide explains that that the original filename and generated stored name are separated. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goTechnical storage → module uploads/{application_id}
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify 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 you’ll accomplish
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.
Follow these steps
- Upload a controlled file.
- Check the display uses the original name/type while storage uses the generated name.
Fields and options to review
Stored filenameGenerated MD5-style unique name
Folder mode0755
File mode0644
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-admin-documents/
Rules the system enforces
- The supplied upload and download controller applies this behaviour.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.