Understand the inline status-action permission limitation
The module’s status endpoint has its explicit edit-permission check commented out. 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 → Lead Filters → Lead Filters
Before you start
- Verify the module is active and use the exact navigation shown above.
- Use an account with the stated module and core CRM permissions.
- Use known test records when changing statuses, visibility, saved filters or global navigation.
What you’ll accomplish
The module’s status endpoint has its explicit edit-permission check commented out. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour using known test leads and a controlled role.
- Verify the core lead status function and role configuration enforce the intended permission.
- Compare with the core Leads workspace.
- Record the verified outcome before changing permissions or code.
Fields and options to review
Verified behaviourThe module’s status endpoint has its explicit edit-permission check commented out.
Rules the system enforces
- The module’s status endpoint has its explicit edit-permission check commented out.
How to confirm it worked
- Understand the inline status-action permission limitation completes without a validation or permission error.
- The refreshed report, menu or saved-template page shows the expected state.
- A second authorised user sees only the records and navigation allowed by their core CRM permissions.
Security, privacy and operational checks
- Test changes with a non-production record or a controlled administrator account before wider rollout.
- Do not use navigation visibility as a substitute for core CRM record permissions.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.