Understand lead-filter template storage
Understand the saved table fields and serialised parameters
Exact navigationAdmin Area → Lead Filters → Lead Filter Templates
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
Understand the saved table fields and serialised parameters The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Use the UI to review name, owner and restored criteria.
- Use activity logs for create/update/delete evidence.
Fields, choices and supported possibilities
idRecord identifier.
filter_nameDisplay name.
filter_parametersPHP-serialised criteria.
staff_idOwner.
Code-backed validations and workflow rules
- Treat serialised parameters as application-managed data.
Expected result and verification
- Understand lead-filter template storage 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.