Understand the client query-string portal routing
This guide explains that why the module renders through the working /clients route. 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 why the module renders through the working /clients route. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Use the menu links generated by the module.
- Do not manually rewrite them to public module routes on this supplied implementation.
Fields and options to review
Index/clients?license_applications=1
Newlicense_applications_action=new
Viewlicense_applications_view={id}
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-setup-access/
Rules the system enforces
- The supplied hooks/controller enforce this behaviour.
How to confirm it worked
- Understand the client query-string portal routing 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.