Every admin dashboard I've worked on had the same problem sooner or later. Someone writes *ngIf="user.role === 'admin'" in a template, someone else adds a guard with its own list of roles, and a month later the menu still shows Billing to people who can't open it. Then the product adds a fourth role and you get to grep the whole app.
In the last dashboard I built (Angular 22, signals, zoneless) I tried to fix that with something boring: a single table that says what each role can do, and everything else asks that table. Menus, routes, buttons, even the mock backend. It's been working well, so here's how it's put together.
If you want to poke at it first, there's a live demo . Open the account menu, pick "Preview as role", then Viewer, and watch half the app disappear.
The table
Components never ask "is this an admin?".…