Understand which tasks a staff member can see
Apply the exact core task-permission scope used by the report query.
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
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.
Exact step-by-step process
- Confirm whether the staff member has the global core Tasks View permission.
- Open the report as that staff member.
- Apply a broad filter such as All Time.
- Compare the result with the core Tasks workspace using the same account.
Fields, choices and supported possibilities
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.
Code-backed validations and workflow rules
- 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.
Expected result and verification
- 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.