User Roles & Security
Role-Based Access Control (RBAC) and authentication security.
UC-CORE-002: User Roles & Permissions
Purpose: Ensure users only access features relevant to their role.
| Property | Value |
|---|---|
| Actor | Admin / System |
| Trigger | User Login |
| Priority | P0 |
Capabilities:
-
Standard Roles:
-
Owner: Full access to all dashboards, revenue, and staff settings.
-
Manager: Access to Staff Schedule, Inventory, and Rosters. No Financials.
-
Front Desk: Access to Calendar, Booking, and Check-in. No Settings.
-
Stylist: Read-only access to own schedule and commissions.
-
-
Custom Permissions:
- Toggle specific actions (e.g., "Allow Front Desk to Refund").
Main Success Scenario:
- "Stylist" logs in.
- Dashboard shows only "My Appointments" and "My Performance".
- "Settings" tab is hidden.
- User tries to access
/admin/revenue-> Redirected to 403 Forbidden.
Acceptance Criteria:
- [ ] Admin can assign roles to new staff invites.
- [ ] UI elements (buttons/tabs) are hidden based on permissions.
- [ ] API endpoints enforce same role checks (Backend validation).
Related Use Cases
-
Tenant Management: Owners manage their staff roles.
-
Staff Attendance: Managers approve leave.