Understand lead-filter template storage
This guide explains the saved table fields and serialised parameters. 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 → Lead Filters → Lead Filter Templates
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
Understand the saved table fields and serialised parameters The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Use the UI to review name, owner and restored criteria.
- Use activity logs for create/update/delete evidence.
Fields and options to review
idRecord identifier.
filter_nameDisplay name.
filter_parametersPHP-serialised criteria.
staff_idOwner.
Rules the system enforces
- Treat serialised parameters as application-managed data.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.