Separate client-visible and internal information
Check the correct field and document before saving or uploading.
Exact navigationAdmin Area → Licence Applications → Case
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
Check the correct field and document before saving or uploading. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the case or storage/audit area described.
- Confirm the intended record and visibility.
- Perform only the authorised action.
- Verify the register, portal and retained evidence after the action.
Fields, choices and supported possibilities
Client visiblelandlord_visible_notes, visible timeline, all supplied staff uploads
Internalinternal_notes
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-deletion-security/
Code-backed validations and workflow rules
- The module applies the stated soft-delete, ownership, visibility or storage behaviour.
Expected result and verification
- Separate client-visible and internal information 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.