Deletion, storage and security

Understand uploaded-file permission modes

This guide explains that the module creates case folders as 0755 and files as 0644. 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.

Audience: CRM staffPermission: Appropriate Licence Applications permissionModule v1.0.0
Jump to steps
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 the module creates case folders as 0755 and files as 0644. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to the case or storage/audit area described.
  2. Verify the intended record and visibility.
  3. Perform only the authorised action.
  4. Check the register, portal and retained evidence after the action.

Fields and options to review

Directory mode0755
File mode0644
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-deletion-security/

Rules the system enforces

  • The module applies the stated soft-delete, ownership, visibility or storage behaviour.

How to confirm it worked

  • Understand uploaded-file permission modes 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

  • Do not expose landlord, property, identity or authority documents beyond their intended audience.
  • Do not delete storage files directly to simulate a module action.