What Eve is allowed to see
The services and records your role can already reach, plus the files you attach to a conversation, such as an availability sheet or a photo of a delivery note.
Most restaurant AI either chats in a vacuum or takes actions nobody can audit. Eve works inside the operating table, within your venue and permission boundaries, and stops at a review point.

Teams that will accept a draft and reject an unsupervised send, publish or payment.
The services and records your role can already reach, plus the files you attach to a conversation, such as an availability sheet or a photo of a delivery note.
Eve reads the venue’s own records and your attachments; it does not invent a guest or a number.
A schedule draft, a validation or an integration setup is a proposal. Approve, edit or reject remains a person-owned control.
Every approved action runs through a named executor and is recorded with who approved it.
Eve reads attachments and proposes schedule drafts, validations, publications and amendments for Team & Payroll, and connection preparation for Integrations. Automation rules persist for review; condition evaluation and content generation stay switched off by default.
StatusRules persist for review; condition evaluation and generation remain unavailable.
No uncontrolled outbound actions, no payments, no publishing without approval, and no claim that every specialist is live.
Every service shares the same account, venues and permissions. Open any of them and the context comes along.
Bring the decisions you will not delegate. That list is the product.