Setup, access and permission scope

Understand Advanced Task Filters

Understand the two workspaces, supported report criteria and personal-template workflow.

Audience: CRM staff and administratorsPermission: Advanced Task Filters: ViewModule v1.0.4
Exact navigationAdmin Area → Task Filters → Task Filters
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 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.

Exact step-by-step process

  1. Open 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. Open Task Filter Templates to load, update or delete a template owned by your staff account.

Fields, choices and supported possibilities

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

Code-backed validations and workflow rules

  • 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.

Expected result and verification

  • 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.