Security, limitations and troubleshooting

Troubleshoot a missing Staff Member filter

The member selector is intentionally shown only to users with global core Tasks View permission. 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: Administrator / authorised CRM staffModule 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

The member selector is intentionally shown only to users with global core Tasks View permission. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Reproduce the behaviour with a controlled staff account and known task records.
  2. Check the user’s core Tasks permission; do not grant broader access solely to expose the selector.
  3. Refresh the page and compare the result with the core Tasks workspace.
  4. Record the outcome before changing permissions or module code.

Fields and options to review

Verified behaviourThe member selector is intentionally shown only to users with global core Tasks View permission.

Rules the system enforces

  • The member selector is intentionally shown only to users with global core Tasks View permission.

How to confirm it worked

  • Troubleshoot a missing Staff Member filter 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.