Skip to main content
GullySystem
Hospitality

Roles and Permissions for Caterers

Control which records and actions each user can access.

Platform

Does this function belong in your operation?

Use when different staff should see or change different business information.

A user joins, changes responsibility or leaves.

The chef sees menus, quantities and cooking sheets. The accountant sees receipts and vendor bills. Only the owner changes a quoted rate once the family has accepted the quotation.

Bring the records the workflow depends on.

  • User list
  • Role responsibilities
  • Record-level access rules

Outputs to check

  • Approved role-access matrix
  • User assignment history
  • Access-review exception list

Follow the roles and permissions workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Map responsibilities

    Identify the records and actions each role needs.

  2. 2. Review sensitive rights

    Separate high-impact actions and define approval authority.

  3. 3. Assign named users

    Grant the approved roles without sharing credentials.

  4. 4. Test access

    Check permitted actions, denied actions and combined-role effects.

  5. 5. Review changes

    Remove obsolete access after transfers, temporary cover or departures.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Owner

Decides who may see money. It is the one setting most owners want to make themselves.

Branch manager

Works inside their own branch and requests anything beyond it.

Office admin

Adds a new joiner to a role on the first morning, and closes it on the last.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Temporary cover required

Grant time-limited authority with an owner and review date.

Conflicting roles assigned

Review combined permissions rather than checking each role in isolation.

User leaves

Revoke access in each connected system and track any unconfirmed closure separately.

Can this work independently?

Permissions operate on the applications and records that enforce them. A documented role matrix alone cannot restrict an unrelated system. Employee or identity-provider links can support joiner and leaver actions, while audit records show assignments and privileged changes.

Systems and records it connects with

  • Audit trail: Actor, timestamp and change evidence for controlled actions.
  • Multi-branch consolidation: Branch identifiers and reconciled combined reporting inputs.
  • Workflow and approvals: Authorised decisions and pending request status.
  • Payroll: Approved pay inputs, deduction calculations and payment instructions.

Configure, test and introduce the workflow.

  • You describe who does what in the business. You get a proposed set of roles to confirm.
  • Cost, margin, wastage and salary visibility are settled. A note records who may see each. Staff are entered with their own sign-in. Shared passwords are retired as people move across.
  • A few staff try their screens on the trial. They tell us what is missing or too open. Gaps are found early. Exceptions granted to individuals are reviewed with the owner. The leaving routine is written down.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Restricted records are inaccessible to unauthorised users.
  • Role changes affect the intended permissions.
  • Departed users lose access as configured.
Caterers

How the business operates.

A caterer may feed a thousand guests at a wedding hall. In the next, the work is lunch for an office canteen every working day.

Event booking with menu versions

Record each event with date, venue, session, count and menu, saving every change as a new version the family approves.

Per-plate costing

Work the ingredient cost of a plate from your recipes, with staff, gas, transport and vessel charges added. The quoted rate sits beside it.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Event order book. Hold every event with its date, venue, session, guest count, menu and client. Two functions on one day appear side by side.
  • Menus with versions. Build menus item by item for each session, save each revision and mark the approved version. The kitchen opens only the approved one.
  • Per-plate costing. Calculate ingredient cost per plate from your recipes, with staff, transport, gas and vessel charges added. The quoted price sits beside the cost.
  • Quotation and advance. Price per-plate rates by session, and counters and live stalls separately, and record the advance and balance.

Operational bottlenecks to check

Menu versions are mixed up

The final menu is agreed by voice note late at night. The kitchen works from an earlier printout. The wrong menu gets cooked.

The real cost per plate is unknown

Groceries for several events are bought together, so it is unclear which event made money. Margins are guessed.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry and quotation

    Record the date, venue, session and approximate count, suggest menus and send a per-plate quotation.

  2. 2. Booking with an advance

    Receipt the advance and block the date against the venue and session. Each menu change saves as a new version, and the family’s approval is recorded against the version they accepted.

  3. 3. Closing count

    The family gives a final figure. Ingredient quantities are worked from your recipes at that count, and the week’s events combine into one purchase list.

  4. 4. Kitchen, staff and vessels

    Assign cooks, servers, cleaners and drivers to the event. Double bookings are flagged early, and vessels go out on a loading list with a return date.

  5. 5. The day at the hall

    The head cook opens the approved menu and quantities on a phone. The supervisor records plates added, late counters and requests made on the spot.

  6. 6. Settlement

    The bill is built from the closing count and additions with the advance deducted. Vessels are checked back in, and the event shows cost against income.

Industry reports to connect with

  • Events by date, with counts and approved menus
  • Cost per plate against the rate quoted
  • Purchase list for the week, across all events
  • Staff and vessel bookings, with clashes marked

Questions before implementation.

When should caterers consider roles and permissions?

Use when different staff should see or change different business information. A user joins, changes responsibility or leaves.

What should we bring to the requirements discussion?

Bring anonymised examples of User list; Role responsibilities; Record-level access rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Control which records and actions each user can access. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Permissions require ongoing ownership and do not replace broader security controls.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Restricted records are inaccessible to unauthorised users. Use this check when reviewing the first working version.

Talk to us

Discuss roles and permissions for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements