Setup, access and permission scope

Understand which tasks a staff member can see

Apply the exact core task-permission scope used by the report query. 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: View plus applicable core Tasks permissionsModule 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

Apply the exact core task-permission scope used by the report query. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Verify whether the staff member has the global core Tasks View permission.
  2. Go to the report as that staff member.
  3. Apply a broad filter such as All Time.
  4. Compare the result with the core Tasks workspace using the same account.

Fields and options to review

Without global Tasks ViewTasks assigned to the staff member are included; when the user has core Tasks Create, tasks created by that staff member are also included.
With global Tasks ViewAll otherwise matching tasks can be included, and an optional staff-member filter becomes available.

Rules the system enforces

  • The module adds its own scope to the query and does not elevate core task access.
  • A staff member without global task view cannot use the report to retrieve unrelated tasks.

How to confirm it worked

  • The scope comparison 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.