Understand the Create-capability limitation
The module registers a Create capability, but the current save-template branch does not perform a separate Create check after View access is granted. 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 → Task Filters → Task 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 registers a Create capability, but the current save-template branch does not perform a separate Create check after View access is granted. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Reproduce the behaviour with a controlled staff account and known task records.
- Grant View only to staff who may also save personal templates, or apply a reviewed code-level permission correction before relying on separate Create governance.
- Refresh the page and compare the result with the core Tasks workspace.
- Record the outcome before changing permissions or module code.
Fields and options to review
Verified behaviourThe module registers a Create capability, but the current save-template branch does not perform a separate Create check after View access is granted.
Rules the system enforces
- The module registers a Create capability, but the current save-template branch does not perform a separate Create check after View access is granted.
How to confirm it worked
- Understand the Create-capability 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.