Security, limitations and troubleshooting

Troubleshoot a lead template that does not load

The filter ID must be numeric, owner-scoped and loaded without a POST request.

Audience: Sales staff and administratorsPermission: Administrator / authorised sales staffModule v1.1.4
Exact navigationAdmin Area → Lead Filters → Lead 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

The filter ID must be numeric, owner-scoped and loaded without a POST request. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Exact step-by-step process

  1. Reproduce the behaviour using known test leads and a controlled role.
  2. Open it from Lead Filter Templates and do not alter the URL.
  3. Compare with the core Leads workspace.
  4. Record the verified outcome before changing permissions or code.

Fields, choices and supported possibilities

Verified behaviourThe filter ID must be numeric, owner-scoped and loaded without a POST request.

Code-backed validations and workflow rules

  • The filter ID must be numeric, owner-scoped and loaded without a POST request.

Expected result and verification

  • Troubleshoot a lead template that does not load 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.