fe-permissions

What problem does it solve?

Inconsistent or missing permission checks in the frontend lead to insecure UI surface and leaked functionality where users can see or act on features they should not access. This Skill provides concrete patterns and rules to centralize authorization checks, avoid fragile role-string logic, and ensure route and component-level protection are applied correctly.

Core Features & Use Cases

• Consistent component checks: Use the permissions store and CASL abilities to show or hide UI elements reliably.
• Route-level protection: Register permissions on sidebar items so AuthRedirect can automatically block unauthorized access and redirect to the 403 page.
• Impersonation safety: Enforce restrictions so impersonated users cannot perform destructive DELETE actions even if abilities allow them.
• Use Case: Add read access to a billing dashboard by updating the sidebar config and verifying that the view redirects unauthorized users to the 403 page.

Quick Start

Add Actions.READ for TenantResourceObjectEnum.BILLING to the sidebar item for /billing and verify AuthRedirect blocks users without that permission.