Understand Dashboard position handling
Know why Dashboard can remain first.
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
Know why Dashboard can remain first. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open the relevant Main Menu or Setup Menu builder.
- Make one controlled change that demonstrates the rule.
- Save and reload the CRM navigation.
- Reset after the test when the change is not required.
Fields, choices and supported possibilities
Code-backed ruleWhen Dashboard is the first submitted item at position 5, the controller forces position 1.
Code-backed validations and workflow rules
- When Dashboard is the first submitted item at position 5, the controller forces position 1.
Expected result and verification
- Understand Dashboard position handling 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.