Restaurant operations guide
Give restaurant staff the access their shift requires
Quick answer
Create roles around duties, grant the smallest useful permission set, and test each role with a non-owner account. Wobistro includes staff management plus role-based permissions across operational modules.
Step-by-step workflow
- List duties for order, menu, reservation, website, and settings work.
- Create roles that match those duties instead of sharing an owner login.
- Grant only the modules each role needs.
- Sign in as a test staff user and verify allowed and restricted paths.
Pre-launch checks
- Former staff accounts are removed promptly.
- Sensitive settings are limited to accountable managers.
- Role changes are retested after new modules are enabled.
Frequently asked questions
Why avoid shared logins?
Individual staff access improves accountability and makes revocation practical.
What is least privilege?
It means giving a user only the access needed for their assigned work.
Should roles mirror job titles?
Only when job titles map cleanly to duties; permissions should follow actual tasks.
Product scope and operator responsibility
Wobistro provides the digital controls referenced in this guide, subject to the active plan and configuration. The restaurant remains responsible for food safety, allergen disclosure, pricing, taxes, payments, staffing, availability, fulfillment, accessibility, and local compliance.