Understand task-filter template storage
This guide explains which data is stored for each personal filter template. 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 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 which data is stored for each personal filter template. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Check the template through the user interface rather than editing the database.
- Verify the filter name, owner and restored criteria.
- Use activity logs to investigate create, update or delete events.
Fields and options to review
idTemplate record identifier.
filter_nameUser-visible name.
filter_parametersPHP-serialised report parameters.
staff_idOwner staff identifier.
Rules the system enforces
- The table name is prefix-aware.
- Serialised parameters should be treated as application-managed data.
How to confirm it worked
- The storage review 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.
- Do not edit serialised values directly in production.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.