Assign View Licence Applications permission
Allow a non-admin staff member to open the register and cases. 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 goAdmin Area → Setup → Roles → Role → Licence Applications → View
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
Allow a non-admin staff member to open the register and cases. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the intended staff role.
- Enable View under Licence Applications.
- Save the role.
- Sign in as a controlled staff user and confirm the menu/register opens.
Fields and options to review
Capabilityview
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
- Assign View Licence Applications permission 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.