Understand task-filter template storage
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains which data is stored for each personal filter template.
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 this guide helps you do
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
idTemplate record identifier.
filter_nameUser-visible name.
filter_parametersPHP-serialised report parameters.
staff_idOwner staff identifier.
Rules and limits
- The table name is prefix-aware.
- Serialised parameters should be treated as application-managed data.
Check 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.
Related guides
Was this guide useful?Your response is stored only in this browser.