Understand the absence of public unauthenticated applications
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Require a signed-in client contact to submit.
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 this guide helps you do
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
Public formNot implemented
Category/help-centre/category/licence-applications/
Topic/help-centre/topic/licence-applications-troubleshooting-limitations/
Rules and limits
- The supplied module implements or omits the function exactly as described.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.