La Comanda is a role-based platform. Every staff member signs in to their designated station — ADMIN, WAITSTAFF, KITCHEN, or BARISTA — and is routed to the view that matches their responsibilities. The sidebar renders only the navigation items that belong to the active role, so each user sees a focused, clutter-free interface. Attempting to visit a module outside your role’s scope triggers the Restricted Access (403) page.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/JAQA20/Paradigmas-G3/llms.txt
Use this file to discover all available pages before exploring further.
Role Overview
Admin
Full access to every module in the platform. Admins can view the live Dashboard, manage the dining room in Table View, monitor kitchen tickets, control Inventory levels, manage staff via Staff Control, and configure the system through Settings.
Waitstaff
Scoped to front-of-house operations. Waitstaff can access Table View to monitor the dining room floor plan, manage active tables, and coordinate order handoffs. They do not have access to back-of-house or administrative modules.
Kitchen
Focused entirely on the Kitchen Display System (KDS). Kitchen staff see the Kitchen Monitor, where incoming tickets are displayed, prioritized, and marked as preparing or ready. They have no access to the dining room or administrative modules.
Barista
A dedicated station role for bar and coffee service. Baristas are routed to their station-specific view and are isolated from both the kitchen and dining room management screens.
Sidebar Navigation by Role
The sidebar is the primary navigation surface in La Comanda. The table below shows which modules each role can access. Modules marked — are not reachable from that role’s sidebar and are enforced at the route level.| Module | Admin | Waitstaff | Kitchen | Barista |
|---|---|---|---|---|
| Dashboard | ✓ | — | — | — |
| Table View | ✓ | ✓ | — | — |
| Kitchen Monitor | ✓ | — | ✓ | — |
| Inventory | ✓ | — | — | — |
| Staff Control | ✓ | — | — | — |
| Settings | ✓ | — | — | — |
signOut() from Clerk’s useAuth() hook and ends the session immediately.
Access Denied Behavior
If a user navigates directly to a URL for a module they are not permitted to access — for example, a Waitstaff member typing/inventory into the address bar — La Comanda renders the /403 Restricted Access page. The page displays the HTTP 403 status, a System ID, the current User ID, and the Access Layer level required (Level: Admin Only for admin-only routes).
To resolve a permissions error, contact your restaurant administrator and request a role elevation. Do not attempt to bypass the route guard; the ProtectedRoute component will intercept unauthorized requests and redirect you before any data is loaded.
Staff Display Labels
Within the Staff Control module, administrators manage team members who appear in the staff table. Each staff record is displayed with one of the following role labels, which correspond to the station types used across the platform:| Display Label | Station |
|---|---|
| Manager | ADMIN |
| Waiter | WAITSTAFF |
| Executive Chef | KITCHEN |
Role enforcement is applied at the route level via the
ProtectedRoute component in App.tsx, backed by Clerk session state. Client-side navigation guards and the Clerk <SignedIn> / <SignedOut> primitives ensure that unauthenticated users are redirected to sign-in and that authenticated users only access routes their session permits.