Sign in to your DineWave account
| Restaurant | Owner | Cuisine | Items | Created | Status | Actions |
|---|
| Name / Email | Role | Restaurant | Last Login | Status | Actions |
|---|
| Time | User | Restaurant | Action | Details | IP |
|---|
Full platform access. Can manage all restaurants, users, view all menus and activity logs. Can create or delete any account. Cannot be deactivated.
Full control over their own restaurant only. Can edit all menu content, restaurant info, branding, and manage their QR code. Cannot access other restaurants.
Read-only access to their assigned restaurant's menu and information. Useful for waitstaff to view the menu. Cannot make any changes.
1. Client sends POST /api/auth/login with email + password
2. Server validates credentials with bcrypt hash comparison
3. On success, a session cookie is set (httpOnly, SameSite=lax, 7-day expiry)
4. Every subsequent request carries the session cookie; server validates role via requireAuth(...roles) middleware
5. For restaurant routes, requireRestaurantAccess verifies the user's restaurant_id matches the requested resource
6. Super admins bypass the restaurant ownership check automatically
Customers scan this to view your menu — no app needed
Scan to view menu
Print this QR on table tents, menu covers, receipts, and entrance posters. When scanned, customers see your full menu instantly — no app needed.
End your current session on all devices.