Team access / Event ops
Keep kitchen, floor, and office on the current plan
Manage My Restaurants Events has no team chat. You run the night from one event plan — and each login only gets the slice their job needs, so the house stays on the latest plan version.
14 days · full features · Start free trial
The mess when the team is not on one plan
When the team is not on one current plan, the house runs on fragments — and group chat is not a system of record.
Email threads
The “final” menu lives in someone’s inbox.
Spreadsheets
Guest counts and duties drift between files.
A photo of the run-of-show in a group chat
Blurry, cropped, already outdated.
Which print is current?
Kitchen and floor argue from different paper.
What the event plan holds
The booking is where title, times, status, category, labels, guest counts, client, menu, additional services, timeline, tasks, schedule, notes, and documents live. Office (owner or manager at the location) builds it on the dashboard. Kitchen and floor open the same event — each with the fields their job needs, not a separate “version in chat.”
See also Menus, Timelines, Tasks, Schedules, Features.
Menu
Meals, drinks, packages, add-on food services; quantities; special notes. Office drafts and publishes.
Additional services
AV, flowers, corkage, and similar: office sees rates; floor sees name, description, quantity.
Shopping list
Produced from menu ingredients and quantities = what to buy, not a stockroom.
Tasks
On this event’s board; templates can copy when confirmed — this night, not a company backlog.
Event notes
Office notepad only.
Who sees what
Four views. Kitchen is its own login — not “staff who cook.” Do not merge kitchen and floor. Managing access is how you keep everyone on the current plan.
Office
Owner or manager at the location
Builds the commercial and ops file: client, prices, draft + publish menu, generate shopping list, edit timeline and share link, full task board, whole rota, documents, event notes, analytics and cost journal where the plan includes them. Managers cannot invite or archive logins — only the organization owner hands out seats.
Kitchen
Separate login
Sees every upcoming event at the location (not only nights they are rostered). Opens published menu (print/preview), read-only shopping list, and own tasks (move between columns only). No client file, no prices, no event notes, no document editor, no run-of-show on the kitchen event screen. Prep guest count is the kitchen number.
Floor
Staff
Never the office dashboard. Enter an event only with a shift or a task on that booking. See published menu without prices, services without rates, full timeline read-only, coworkers’ name + job title only, and own tasks to move. Own schedule screen. No client, documents, event notes, shopping-list editing, or plate cost.
Share link
No login
Unlisted view of the current run-of-show (title, groups, step titles, descriptions, times). Not a password portal and not a place to reply. Default expiry: event end + 24 hours if unset. Regenerating the link kills the old URL; expired links are gone. Office can limit which timeline groups are included. Use this when someone needs timing without a seat.
| Role comparison | Owner | Manager | Staff | Kitchen |
|---|---|---|---|---|
| Where | Every location + org | Office dashboard assigned | Staff home | Kitchen event list |
| Events | All | All at location | Shift or task only | All upcoming at location |
| Client / prices / notes / docs | Yes | Yes | No | No |
| Menu | Draft + publish | Draft + publish | Published, no prices | Published, print |
| Shopping list | Generate + mark purchased | Same | No | Read-only |
| Timeline | Edit + share | Edit + share | Read-only when assigned | Not on their event screen |
| Tasks | Full board | Full board | Own cards move | Own cards move |
| Schedule | Whole rota | Whole rota | Own shifts | No schedule screen |
| Team admin | Invite, roles, archive, billing | Roster only — no logins | Own password | Own password |
How a change lands
Nothing pushes into an open tab. The next open of the event, published menu, or share link loads what was last saved or published — that is how the team stays current.
Publish the menu
Draft saves stay in the office. Publish stores a numbered kitchen version with time and author. Kitchen and floor read that version; if never published, kitchen has no current menu.Generate the shopping list again when the menu changed
The list is produced from this menu. It does not rewrite itself when a dish changes. After menu changes, generate again so kitchen is not buying old dishes.Share link loads current times
Not a photo from the briefing. Until expiry or replace, the link shows the timeline as it is now.Assigned people move their own tasks
Kitchen and floor move only their cards on the same board. They cannot rename, rewrite, reassign, create, or delete cards.
How people get in
Employee
A roster row at the location (name, email, job title, phone). Can exist with no login. Not a billed seat. Used for shifts and task assignment.
Login
A user account with a role at one or more locations = a seat. Only the organization owner invites. Pending invites reserve a seat until accept, cancel, or expire (7 days). Archive frees the seat immediately. The owner is not counted as a seat. One person at several locations in the same org = one seat.
Invite flow
Owner picks active locations, then invites a new person (email, name, role, optional job title/phone) or — when a single location is selected — invites an existing employee to log in (email must match). Staff/kitchen emails say so; manager gets a generic team invite. Managers manage the roster only — they cannot create logins.
Roles you can assign
Manager, Staff, Kitchen. Manager at one location cannot also be staff/kitchen anywhere in the same org. Staff and kitchen can combine across locations.
What you are not buying
No team thread
Alignment is the shared plan, not a chat.
No warehouse
Shopping list is a buy-list from the menu, not stock.
No payroll
Schedules and who is on the night; not HR pay runs.
- Not a POS
- Not a hotel PMS
- Not guest messaging
Frequently asked questions
No. Communication means the shared event plan: published menu, timeline, tasks, and optional unlisted share link — not a message thread.
No live push. The next time someone opens the event, the published menu, or the share link, they see the last saved or published state.
Save keeps a draft in the office. Publish stores the numbered kitchen version kitchen and floor read. If you never publish, kitchen has no current menu.
No. Office generates it from the current menu. After the menu changes, generate again so kitchen is not buying old dishes. It is a buy-list, not a storeroom.
No. Kitchen is a separate login. Kitchen sees upcoming events at the location; staff open nights they are on (shift or task). Kitchen’s event screen does not include the run-of-show.
Only the organization owner. Managers can manage the employee roster but cannot create or archive login accounts.
An employee is a roster row and can exist without a login (not a billed seat). A login is a seat with a role. Seat totals depend on your plan — we do not hard-code a number here.
Current run-of-show fields (title, groups, steps, descriptions, times). It is not a reply portal. It expires (default: event end + 24h if unset); regenerating kills the old URL.
No. Kitchen neither. Those stay with office roles.
Publish the menu they should cook and serve, regenerate the shopping list after menu changes, and keep timeline edits in the event (or share link) — not in a group chat photo.
Yes — 14 days with full features. Try for free from this page.
Native apps exist for these roles in the product. This page does not claim App Store / Play listing status — use the trial in the browser to evaluate.