Understand generated document storage names
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that that the original filename and generated stored name are separated.
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 this guide helps you do
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
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 and limits
- The supplied upload and download controller applies this behaviour.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.