Troubleshoot a client portal route problem
Use the supplied /clients query-string links rather than unavailable public module routes.
Exact navigationClient Portal → Licence Applications
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
Use the supplied /clients query-string links rather than unavailable public module routes. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the exact workspace stated above.
- Confirm activation, permission, ownership, field validation and supporting service configuration.
- Apply only the corrective action supported by the supplied code.
- Retest with a controlled case.
Fields, choices and supported possibilities
Working base/clients?license_applications=1
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-troubleshooting-limitations/
Code-backed validations and workflow rules
- The supplied module implements or omits the function exactly as described.
Expected result and verification
- Troubleshoot a client portal route problem 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.