Security, limitations and troubleshooting

Understand unsupported audit, import, export and user preview

No module activity log, configuration import/export or preview-as-user workflow is implemented. 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 administratorsPermission: Administrator / technical supportModule v2.3.0
Jump to steps
Where to goAdmin Area → Setup → Menu Setup
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

No module activity log, configuration import/export or preview-as-user workflow is implemented. 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 administrator account.
  2. Record changes through your change process and test with controlled accounts.
  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 and options to review

Verified behaviourNo module activity log, configuration import/export or preview-as-user workflow is implemented.

Rules the system enforces

  • No module activity log, configuration import/export or preview-as-user workflow is implemented.

How to confirm it worked

  • Understand unsupported audit, import, export and user preview 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.