Solutions
Roles and permissions in meal-plan software
A meal-plan system holds names, phone numbers, home addresses and health information. Who can see which parts of that is a privacy decision before it is a convenience one.
Different jobs need different slices
A cook needs totals per recipe and nothing else — customer names are noise on a production list. A packer needs names and allergens but no addresses. A driver needs addresses and item counts for their own stops today, and no financial data at all.
Giving everyone the full record is simpler to configure and creates an unnecessary exposure surface, particularly for a workforce with normal turnover.
A sensible default set
Kitchen
Production lists, recipes, allergen conflicts. No addresses, no billing.
Packing
Per-customer portions and labels. Names and allergens, no financial data.
Driver
Their own stops for today only, with addresses and item counts, and the ability to close a stop out.
Office
Customers, subscriptions and changes, with every action attributed.
Owner
Everything, including billing and reporting.
Scoping matters as much as roles
A driver limited to the driver role but able to see every driver’s stops has been given the whole delivery book. Scoping — to their own stops, for today — is what makes the role meaningful.
The same applies to attribution. Roles limit what someone can do; the audit trail records what they did, and you need both to answer a question about a change made three weeks ago.
Common questions
- Why should kitchen staff not see customer addresses?
- Because they have no operational use for them, and every additional person with access to home addresses is exposure without benefit. A cook needs totals per recipe, not names.
- Should drivers see all stops or only their own?
- Only their own, for today. A driver who can see every route has effectively been handed the entire delivery book, which is a meaningful privacy exposure with no operational upside.
- Do roles remove the need for an audit trail?
- No, they are complementary. Roles limit what someone can do; the audit trail records what they actually did. Answering a question about a change from three weeks ago needs the second.
See it running against a real kitchen
The product pages show the actual admin loaded with a demonstration kitchen — production, packing, routes and the dashboard, exactly as an operator sees them.
Related reading
- SolutionsThe customer record in a meal-plan business is an operational documentIn most industries a CRM is a sales tool. In a meal-plan kitchen the customer record drives what gets cooked and where it goes, which makes it the most operationally dangerous data in the business.
- SolutionsMeal delivery software for operations managersAn operations manager is judged on whether today went out correctly. That makes their evaluation criteria different from an owner’s, and mostly about exceptions rather than features.
- SolutionsMeal delivery management software for the daily operating rhythmEvery meal-plan business runs the same loop every single day — cook, pack, drive, confirm. Management software earns its place by making the current position of that loop visible without anyone compiling it.
- SolutionsMeal delivery software for kitchen managersA kitchen manager needs one thing from software above all others: a number they can trust before they start cooking, that nobody will change halfway through the morning.
- SolutionsWhy a meal business needs a change historyAn audit trail sounds like compliance furniture until the first time a customer insists they paused, a staff member insists they applied it, and the boxes went out anyway. Then it is the only thing that resolves the question.