navigation

Declare the item once in the menu declaration file with its title, path, and icon, then reference the same route constant in the section's routes file. The single declaration feeds both the rendered menu and the route access guard, so the two never drift apart.

Use two-layer gating: set the required user right in the item declaration, and the route guard reads that same declaration. An item gated by a section flag is declared without an address and without rights, since there is no screen to open.

This happens when route gating uses a separate list from the menu declaration, and the two drift apart. The rule requires one declaration to serve as the source of both menu visibility and route guards, so a hidden item is also unreachable.

No. The declaration must not import the shell, because that closes a dependency cycle between shell, container, and feature modules and breaks the layout boundary check. Domain data reaches the header through an injection token instead.

Provide it through an Angular InjectionToken defined in the container util layer, with the composition root binding the token to the implementation. The declaration itself never imports the application shell or feature code directly.