Understand the template-update ID limitation
The model update method applies by template ID after the normal controller load; the model method itself does not add a staff-owner condition to the update query. 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 model update method applies by template ID after the normal controller load; the model method itself does not add a staff-owner condition to the update query. 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.
- Use only the owner-scoped interface and prevent URL or request manipulation; consider a reviewed owner condition in a future module release.
- 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 model update method applies by template ID after the normal controller load; the model method itself does not add a staff-owner condition to the update query.
Rules the system enforces
- The model update method applies by template ID after the normal controller load; the model method itself does not add a staff-owner condition to the update query.
How to confirm it worked
- Understand the template-update ID 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.