This project is not covered by Drupal’s security advisory policy.
This module provides a menu blocks for primary and secondary navigation, with a source menu being selected per role.
Features
- Role-based menu sources: choose which primary and secondary menus each role should see.
- Priority ordering: weight-based evaluation lets you define which role mapping wins when users have multiple roles.
- Single block, dynamic output: place one block and it renders the correct menu per user.
Post-Installation
- 1. Configure the module:
- Go to the configuration page at /admin/structure/menu/sources and map roles to their primary and secondary menus.
- Arrange role mappings with weights to control which mapping wins when users have multiple roles (lower weight = higher priority).
- Place the block:
- Open Block layout and add the “Menu block (from Main Menu Src settings)” to a region.
- Optionally adjust menu display settings (levels, depth, expand behavior, label/title behavior).
-
Verify:
- Log in as users with different roles to confirm the correct menus are rendered.
- If you update role mappings later, clear caches or let Drupal’s cache tags refresh automatically.
Special considerations:
- When a user has multiple roles, the mapping with the highest priority (lowest weight) is used.
- If no menu is configured for a role, the site’s default menu can be used as a fallback.
Additional Requirements
- Drupal core’s Menu and Block systems enabled.
- Contributed “Menu Block” module to provide the advanced menu block behavior this project builds upon.
Project information
Minimally maintained
Maintainers monitor issues, but fast responses are not guaranteed.Maintenance fixes only
Considered feature-complete by its maintainers.- Project categories: Site structure
- Created by alex.bukach on , updated
This project is not covered by the security advisory policy.
Use at your own risk! It may have publicly disclosed vulnerabilities.
