Remove an existing Main Menu icon
Save an explicit no-icon state instead of reverting to the original. 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.
Where to goAdmin Area → Setup → Menu Setup → Main Menu
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
Save an explicit no-icon state instead of reverting to the original. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Follow these steps
- Go to item options.
- Clear/remove the original icon value as supported by the form.
- Save.
- Verify no icon is displayed.
Fields and options to review
False icon stateRepresents an intentional no-icon override.
Rules the system enforces
- An unchanged original icon is stored differently from an intentionally removed icon.
How to confirm it worked
- Remove an existing Main Menu icon 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.