For Administrators

Administrators configure PrepTable for a customer: who can do what, what campuses exist, where the catalog data lives. The other audiences (floor staff, managers) work within the configuration you provide.

This section covers what an administrator owns and the parts of PrepTable only an admin can touch.

What you own

• Users & roles — inviting staff and managers, assigning campuses, granting or revoking the admin role. Last-admin protection is enforced: the system will refuse to demote the only remaining admin, or to remove the only passkey from a user.
• Campuses (locations) — the per-campus operational scope. Adding a campus is a structural change because it determines which menus, pars, POs, and kitchen queues need to be set up.
• The catalog — items, recipes, vendors. These are global (not per-campus) and changing them affects every campus at once.
• API integrations — Saavor webhook secrets, kiosk tokens. Each kiosk is a service account with its own passkey, scoped to a single campus.
• The audit log — a read-only, append-only trail of every mutating change. Admin-only access.

What's outside your scope

You cannot change menu state directly — that's manager-of-location scoped. You can read any campus's menu, but to make the actual "this menu fires at this campus on this day" change, you work through a manager, or you temporarily grant yourself manager scope for that campus. (Admins do, however, own the menu definition — the recipes and the meal meta — because that's catalog-level.)

You cannot create or edit items on the floor — every stock movement, every order push, every recipe reprice is logged automatically.

Pages in this section

• Roles & campus permissions — the RBAC model and how to grant scope correctly
• The audit log — what gets recorded, how to read it, how long it's retained
• Train-the-trainer guide — a facilitation outline for whoever will deliver this material to a campus team