Security, limitations and troubleshooting

Troubleshoot a missing menu item

Core permission, module activation, saved disabled state or stale runtime registration may hide it.

Audience: CRM administratorsPermission: Administrator / technical supportModule v2.3.0
Exact navigationAdmin Area → Setup → Menu Setup
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

Core permission, module activation, saved disabled state or stale runtime registration may hide it. 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 with a controlled administrator account.
  2. Confirm the feature exists, reset the relevant menu, review permissions and reload.
  3. Test the resulting navigation with an administrator and a restricted staff account.
  4. Reset or restore the intended menu configuration after the test.

Fields, choices and supported possibilities

Verified behaviourCore permission, module activation, saved disabled state or stale runtime registration may hide it.

Code-backed validations and workflow rules

  • Core permission, module activation, saved disabled state or stale runtime registration may hide it.

Expected result and verification

  • Troubleshoot a missing menu item 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.