For schools and administrators

See the whole cafeteria. Know what needs attention next.

Bring school readiness, people, permissions, live service, wallet activity, payments, reporting, and governance into one school-scoped administrative story.

  • Actionable school readiness
  • Responsibility-based access
  • Connected operational oversight

Staff dashboard

Today’s cafeteria operations

School scoped

Today’s sales

$3,047.85

Orders

407

Wallet risk

12

Readiness issues

1

Today’s service

3 serving lines

Main Lunch · Open248 orders
Express Line · Open111 orders
Breakfast · Processed48 orders
Readiness, service, finances, and follow-up in one view

Experience school-level oversight

Move from today’s operation to the next responsible action.

Explore sample dashboard signals, complete a launch-readiness checklist, and compare role-based workspaces. The experience follows the real administrative model while remaining completely separate from school records.

This public preview does not call application APIs, change permissions, or access school data.

Interactive school operations preview
Sample data • no school records are accessed

Sample school workspace

Salesian High School · Administration

Staff dashboard

Today’s cafeteria operations

Sales, orders, wallet risk, and service readiness in one place.

Sales

$3,047.85

Completed cafeteria orders

Orders

407

Open and completed orders

Wallet risk

12

Low balances or failed top-ups

Readiness issues

1

Line configuration follow-up

Service lines

Live readiness and order volume

Main LunchOpen
248 orders
Express LineOpen
111 orders
BreakfastProcessed
48 orders

Needs attention

Exceptions worth reviewing

12 low-balance households

Review available funds and notification status

1 failed top-up

Payment did not increase the household wallet

1 line without today’s service window

Confirm menu, hours, and line status

Explore a sample school workspace from daily oversight to role boundaries.

One school workspace, clear responsibilities

Coordinate the operation without giving everyone the same access.

School administration connects the configuration, people, funds, service, and evidence behind cafeteria operations. Roles and permissions keep those connected workflows appropriately bounded.

01

Make launch and daily readiness visible

Track the operational dependencies behind a usable cafeteria, from payment setup and linked people to active items, menus, and serving lines.

  • Eight-step school readiness
  • People and household relationships
  • Usable menus and serving lines
02

Control access by staff responsibility

Shape each workspace through active-school membership, role priority, and specific permissions instead of giving every staff member broad administration.

  • School-scoped membership
  • Role and permission boundaries
  • Separated sensitive responsibilities
03

Turn activity into responsible follow-up

Use dashboard signals, detailed reports, wallet context, and audit history to understand service results and the exceptions that require attention.

  • Daily service and wallet signals
  • Payment and balance context
  • Reports, audit, and compliance evidence

From readiness to reconciliation

Give every operational state an owner and a next step.

A useful administration workspace does more than display totals. It connects setup dependencies, staff responsibility, live service, financial exceptions, and the evidence needed after the day ends.

  1. 01

    Prepare the school

    Make payment setup, people, items, menus, and serving lines visible through one readiness checklist.

  2. 02

    Assign responsibility

    Give each staff member a school-scoped role that matches the work they are expected to perform.

  3. 03

    Run today’s service

    Monitor sales, orders, serving lines, wallet holds, and exceptions while cafeteria service is active.

  4. 04

    Review and reconcile

    Use reporting and audit context to understand the activity behind balances, payments, and operational results.

Active-school context

Keep every administrative action anchored to the selected school.

Membership and active-school context prevent a shared user account from blending records or responsibilities across schools.

Role-aware workspace

Show staff the tools their responsibilities require.

Checkout, reporting, wallet, people, configuration, payment setup, and security responsibilities can remain distinct.

Financial clarity

Separate balances, holds, payments, and adjustments.

Administrators can follow the account movements behind the number instead of treating every financial event as the same state.

Traceable administration

Pair sensitive actions with permission and audit boundaries.

Role controls, audit history, compliance readiness, incident records, and privacy workflows support accountable school operations.

A school administrator reviewing cafeteria operations

Administrative confidence

See what is ready, what needs attention, and who can take action.

Built around accountability

Keep access, financial activity, and follow-up explainable.

Administrators need operational reach without erasing responsibility boundaries. The workspace keeps the active school, assigned permissions, account context, and audit evidence close to each decision.

  • Scoped access

    School membership, role, permissions, and active-school context shape every authorized workspace.

  • Financial context

    Payments, wallet balances, open-order holds, adjustments, and reports retain distinct meanings.

  • Governance evidence

    Audit history, compliance readiness, incident tracking, and privacy workflows support follow-up.

Frequently asked questions

What school leaders ask about administration and oversight.

Need to map staff responsibilities, payment setup, service readiness, or reporting to your school? We can walk through the complete administrative model.

Can access be limited by staff responsibility?

Yes. The effective workspace is based on active school membership, assigned roles, individual permission grants, and the currently selected school context.

Can one administrator work with more than one school?

A user can have authorized memberships in multiple schools. The active-school context keeps records, configuration, permissions, and actions scoped to the school currently being managed.

How does a school know when cafeteria setup is operational?

The readiness checklist evaluates payment and payout setup, additional staff, households, linked students and guardians, active items, a usable menu, and an active serving line connected to that menu.

What is the difference between the dashboard and reports?

The dashboard provides a quick operational read of sales, orders, service readiness, wallet risk, and exceptions. Reports provide the date ranges, groupings, and detail needed for deeper review and reconciliation.

Give school leaders a clearer path from readiness to reconciliation

Explore how staff access, daily oversight, wallet context, reporting, and governance would fit your cafeteria operation.