Understand the template-update ID limitation
The model update condition uses the template ID after the controller load and does not independently add staff ownership.
Exact navigationAdmin Area → Lead Filters → Lead Filters
Before you begin
- Confirm 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 covers
The model update condition uses the template ID after the controller load and does not independently add staff ownership. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Reproduce the behaviour using known test leads and a controlled role.
- Use the owner-scoped UI and prevent request manipulation.
- Compare with the core Leads workspace.
- Record the verified outcome before changing permissions or code.
Fields, choices and supported possibilities
Verified behaviourThe model update condition uses the template ID after the controller load and does not independently add staff ownership.
Code-backed validations and workflow rules
- The model update condition uses the template ID after the controller load and does not independently add staff ownership.
Expected result and verification
- 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.