rbac-pin-security

To enforce role-based access control and PIN authorization, you wrap sensitive UI actions like inventory adjustments or discounts in a PIN modal. This verifies the user's hierarchical role and requests supervisor PIN confirmation when configurable thresholds are exceeded.

Hierarchical role checking for route protection works by validating the user's role against definitions in your auth domain logic. The middleware blocks access if the user's role is lower than the required hierarchy level for the protected route.

Yes, you can disable email and password authentication by prohibiting those login forms. The system enforces a zero email/password policy, requiring authentication via branch selection, user selection, and a 4-digit numeric PIN pad.

The best way to require a supervisor PIN for high-threshold inventory adjustments is wrapping the handler with a ManagerPinModal. This verifies the user's role and prompts for supervisor PIN authorization for adjustments exceeding 100 units.

You need to request a PIN for critical operations when actions exceed configurable thresholds, such as stock adjustments over 100 units, discounts over 10%, or batch deletions. These actions trigger PIN modals tied to higher authority levels.

A 4-digit PIN authentication flow prevents unauthorized executions in critical operations by enforcing hierarchical access control. Disabling email and password authentication in favor of branch, user, and PIN selection eliminates common credential vulnerabilities in sensitive environments.