Roles & Permissions Matrix
What each role may do, and — more importantly — which of those you can actually change from this screen. Granted directly is a filled toggle and it moves; inherited from the role is outlined, already on, and locked.
The decision inside it
The revoke bug nobody catches until an audit
Draw both as the same checkbox and an admin clears one, watches it go empty, and leaves — while the person keeps the access, because it never came from that box. Pressing an inherited toggle here says where the permission comes from and what to change instead.
Installation
How you get it
One command. The CLI writes the file into components/ui/ and installs what it needs.
npx shadcn@latest add https://layropro.com/r/permissions-matrixPro components need the CLI token from your account page. Put it in your environment as LAYRO_KEY and use the namespaced form.
API
“Copy prompt” above puts a full brief on your clipboard — install command, dependencies, props, and the mistakes an assistant usually makes with this component.
Props
Read from the component’s own TypeScript interface when the site is built, so this table cannot drift from the file you install.
| Prop | Type | Notes |
|---|---|---|
permissions | Permission[] | — |
roles | AssignableRole[] | Columns, most privileged first. Default: admin, member, viewer. |
title | string | — |
readOnly | boolean | Read-only mode: every toggle locks, and the legend says so. |
onChange | (next: Permission[]) => void | Fired with the full next list after every change that lands. |
Dependencies
npm packages
clsxframer-motionlucide-reacttailwind-mergeLayro foundations, installed alongside it
layro-themerole-chipLifetime access
Every component, and everything we ship next.
- All 65 components, source included
- The template, and everything released after you buy
- shadcn CLI or download — React 18/19, Tailwind v4
- One payment. No subscription.