Permission Matrix
A permission matrix shows which roles can do each action in a chosen area. It makes access rules easier to compare.
Another example
An owner compares what Admin, Editor, and Viewer can do before changing project access.
Main parts
- 01Roles
- 02Actions
- 03Resource scope
- 04Inherited rules
- 05Effective access
- 06Server enforcement
Use it when
Use it when several roles need a clear comparison across the same actions and scope.
Do not use it when
Do not treat the grid as security by itself. The server must check the current user and resource on every request.
Name used in code
role × permission × scope → configured and effective access Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Permission Matrix to solve this user need without losing the current context. User context: An owner compares what Admin, Editor, and Viewer can do before changing project access. Recommended pattern: Permission Matrix. Why it fits: Use it when several roles need a clear comparison across the same actions and scope. Do not use it when: Do not treat the grid as security by itself. The server must check the current user and resource on every request. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Permission Matrix. Definition: A permission matrix shows which roles can do each action in a chosen area. It makes access rules easier to compare. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.