Understand the absence of public unauthenticated applications
Require a signed-in client contact to submit. 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 → Sign in → 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
Require a signed-in client contact to submit. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the exact workspace stated above.
- Verify 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 and options to review
Public formNot implemented
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-troubleshooting-limitations/
Rules the system enforces
- The supplied module implements or omits the function exactly as described.
How to confirm it worked
- Understand the absence of public unauthenticated applications 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.