Setup, access and permission scope

Understand Advanced Task Filters

This guide explains the two workspaces, supported report criteria and personal-template workflow. 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.

Audience: CRM staff and administratorsPermission: Advanced Task Filters: ViewModule v1.0.4
Jump to steps
Where to goAdmin Area → Task Filters → Task Filters
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 two workspaces, supported report criteria and personal-template workflow. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Task Filters from the administrator sidebar.
  2. Use the report workspace to select criteria, grouping and hidden/export columns.
  3. Apply the filter to refresh the result table.
  4. Save a named template when the same report will be used again.
  5. Go to Task Filter Templates to load, update or delete a template owned by your staff account.

Fields and options to review

Report workspaceBuild and run a task report.
Template workspaceManage saved personal report definitions.
Module version1.0.4.

Rules the system enforces

  • The module adds report tools; it does not replace the core task list or Kanban views.
  • Core task permissions still decide which task rows a staff member can retrieve.

How to confirm it worked

  • The module overview check 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.