Create and edit licence cases

Complete the Landlord-visible notes field

Write only information suitable for the authenticated client. 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: Create or Edit Licence ApplicationsModule v1.0.0
Jump to steps
Where to goAdmin Area → Licence Applications → New/Edit Application → Landlord-visible notes
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

Write only information suitable for the authenticated client. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to the new or edit case form.
  2. Find Landlord-visible notes.
  3. Enter or select the value described in this guide.
  4. Save the case.
  5. Reopen the case and verify the stored value.

Fields and options to review

FieldLandlord-visible notes
Payload keylandlord_visible_notes
Supported valueVisible on the client case page
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-create-edit/

Rules the system enforces

  • Write only information suitable for the authenticated client.
  • Case editing writes this field to the application record unless a dedicated workflow rule is stated.

How to confirm it worked

  • Complete the Landlord-visible notes field 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.