Understand the inline status-action permission limitation
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
The module’s status endpoint has its explicit edit-permission check commented out.
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 this guide helps you do
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
Verified behaviourThe module’s status endpoint has its explicit edit-permission check commented out.
Rules and limits
- The module’s status endpoint has its explicit edit-permission check commented out.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.