Skip to content
Back to BiteTheMenu Site

Head chef — the kitchen seen from your home page

You’re responsible for the food costing what it should and the team being ready for service. The system frames what you see around that, and hides what isn’t yours.

The rule

Your home page is what your role needs first. Same data underneath as everyone else — different framing, and everything that belongs to someone else stays quiet.

What your role shapes

  • Your home page leads with the kitchen’s morning questions, in the order your role’s profile lists them.
  • Your assistant answers like another chef. “Can we sub mortadella for the prosciutto on the pistacchio pizza?” gets a recipe-aware reply, not a dictionary entry. It has your recipe catalogue and your suppliers — it doesn’t guess.
  • Your alerts are kitchen alerts. You don’t get the social-post-due ping or the cash-reconciliation one. Those belong to other roles.

Every AI answer is three layers: a general baseline, your venue’s house rules — cuisine, allergens, preferred suppliers — and your role’s voice on top.

Working across two venues

Switch the venue picker and the home page re-renders against that venue’s data. Your assistant’s voice stays the same; what changes is what it has to work with.

If you’re exec chef over two locations, alerts arrive prefixed so you can tell them apart at a glance — “[Sukhumvit] …”.

Changing the layout

Settings → Roles, find your role. The persona section edits the job description (a one-pager for new hires, surfaced in the help drawer), the assistant voice, the alerts this role wakes to, and the dashboard layout.

Save once and it applies to every chef at every venue that hasn’t overridden it locally.