Understand authenticated-client access
This guide explains that that the supplied guard allows any logged-in client, not only a landlord group. 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 goClient Portal → Licence Applications
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 supplied guard allows any logged-in client, not only a landlord group. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Sign in with a controlled client account.
- Verify the menu appears.
- Apply customer ownership rules to every case and document.
Fields and options to review
Actual guardAny logged-in client with valid client ID
Legacy intentLandlord group check is not enforced
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-setup-access/
Rules the system enforces
- require_landlord explicitly permits any logged-in client.
How to confirm it worked
- Understand authenticated-client access 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.