KAS F&B Nexus — Use cases by role

Tiếng Việt: Use case theo vai trò

Everyday why and how people use Nexus—not a test checklist. For hands-on UI steps, see the manager & staff guide and floor employee guide.

---

Server (Staff mobile)

Use case	What they do
See today’s work	Check assigned checklists on Home / Tasks
Complete checklists	Finish opening/closing steps; attach photo/video evidence when required
Read playbooks	Browse read-only Manuals for their branch and position
Check shifts	View personal shifts (start/end, branch) on Schedule
Request time off	Submit leave dates from the account menu; track approval status
Set availability	Mark days and hours they can work so managers can schedule
Record salinity	Submit reading + meter photo for scheduled broth slots
View roster profile	Read Profile information (changes go through manager/HR)
Receive alerts	Push for new tasks, overdue tasks, salinity reminders

---

Restaurant Manager (Digital Manager)

Use case	What they do
Monitor floor tasks	Task Manager → Task Streams — progress and overdue by branch/position
Assign work immediately	Manual templates → Assign to a named person or everyone with a position in a branch
Maintain playbooks	Task Manager → Manual templates (opening/closing, recurrence, photo rules)
Manage shift templates	Task Manager → Shift templates — reusable windows (e.g. “Lunch 10–16”)
Build and publish schedules	Schedule & roster → Shift schedule — place blocks, then publish
See who’s on today	Schedule & roster → Today's roster
Review availability & time off	Schedule & roster → Team availability and Time off approvals
Follow up on broth checks	Salinity — today's checks, acknowledge missed slots
Handle maintenance tickets	Maintenance requests — approve/reject/resolve with evidence
Manage roster	Settings → Employees — add/edit, branch assign, invitations
Request hires	Recruitment requests — branch staffing needs (Phiếu form)
Export schedule	Schedule & roster → Export spreadsheet (CSV)

Scope: assigned branch(es) only—no data from unassigned locations.

---

Head Chef (Digital Manager + mobile)

Use case	What they do
Yield KPI oversight	Yield reports and activity (receiving/returns/waste)
Log yield on the floor	Mobile Yield capture
Monitor salinity	Today’s checks — branch timeline; acknowledge missed slots
Record salinity on the floor	Mobile Salinity check
BOH playbooks	Kitchen Manual templates (prep, closing, etc.)
Kitchen scheduling	Edit Shift schedule for assigned branches
Store requests	Create or resolve kitchen equipment/supply tickets

---

HR (Digital Manager)

Use case	What they do
Review hiring requests	Inbox of branch manager Recruitment requests
Approve or reject	Review headcount/JD; Approve or Reject with reason
Mark hire complete	Completed after onboarding
Assist roster	Settings → Employees when permissions allow

Scope: Recruitment requests hub—not full Operations.

---

Brand Manager (Digital Manager)

Use case	What they do
Brand-wide operations	All branches — yield, salinity, workforce, store
Yield catalog	Item Category — ingredients and packaging master data
Salinity setup	Pho types (broth standards) + Branch settings (enable, notify)
Store catalogs	Vendors and Equipment master lists
Switch brands	Brand dropdown when running multiple lines
Review platform roles	Settings → Platform roles (read-only)

---

IT Admin (Digital Manager)

Use case	What they do
Full platform configuration	All Settings tabs — brands, branches, employees, roles
Org structure	Create/rename/delete empty Brands / Branches
Permission design	Platform roles permission matrix
People and invitations	Employees — roster, Clerk invitation, cross-brand assign
All-branch access	Implicit access to every branch; set primary home branch
Initial module setup	Yield, salinity, store catalogs (often with Brand Manager)

---

Module use cases (by feature)

Workforce (Tasks + Schedule)

Use case	Description
Path A — One-off task	Manager adds a single checklist line from Task Streams
Path B — Playbook push	Assign a Manual template for an instant bundle
Path C — Schedule automation	Published shifts + playbook binding → tasks drop on the right shift
Evidence audit	Required photo/video steps; managers review proof in Streams
Overdue follow-up	Overdue filters + push notifications

Yield

Use case	Description
Receiving log	Log inbound quantities
Vendor return	Log returns to suppliers
Waste log	Log spoilage/disposal
KPI review	Reports and activity by branch/brand

Salinity

Use case	Description
Broth QC schedule	Time slots per pho type (e.g. hourly)
On-site reading	Staff submit meter photo + reading
Missed follow-up	Notify list alerts; manager acknowledge
Brand-wide broth standard	Min/max range and active windows per pho type

Store / Maintenance

Use case	Description
Purchase request	Request supplies to buy
Facility issue	Report broken equipment or facilities
Approval workflow	Submit → approve/reject → resolve with evidence
Catalog reference	Pick vendor / equipment on tickets

Recruitment

Use case	Description
Headcount request	Branch manager digital form to HR
HR pipeline	Pending → Approved/Rejected → Completed
Audit trail	Status and rejection reasons recorded

---

Brand and branch context

Use case	Description
Single-brand store	One brand (e.g. Pho100)—no brand switching
Multi-brand operator	Separate catalogs, roster, and requests per brand
Cross-brand employee	One login; Manage assigned brands + in-app brand switch
Branch-scoped manager	Restaurant Manager / Head Chef — assigned branches only

---

Not in scope today

Item	Status
Attendance (GPS clock-in, punch history)	Not released
Public self sign-up	Invite-only when ONBOARDING_STRICT is on

---

Role × module at a glance

	Tasks/Schedule	Yield	Salinity	Store	Recruitment	Settings
Server	● mobile	● capture	● capture	● submit	—	—
Restaurant Manager	● full	● view	● view	● process	● create	● branch roster
Head Chef	● BOH	● full	● full	●	—	—
HR	—	—	—	—	● full	○ assist
Brand Manager	● all branches	● catalog	● setup	● catalog	●	○ read
IT Admin	● all	● all	● all	● all	●	● full

● primary use · ○ limited

Related: Public Use cases. Pilot QA checklist (internal): docs/internal/ in Git.