Release notes & training material

This section gives (1) a release-notes template for documenting future changes, and (2) training material, a curriculum and role-based learning paths a trainer can teach from and a support technician can reference.

Part 1, Release notes

HappierBiz improves continuously. Use this template to record what changed for your team each time. (No version history is reproduced here; fill it in as releases land.)

Release notes template

## <Date>, <short title>

**New**
- <feature>, <one line on what it does and who benefits>

**Improved**
- <change>, <what's better>

**Fixed**
- <issue>, <what was wrong, now resolved>

**Action needed (if any)**
- <e.g. "Owners: review the new permission X in Team → Staff list">

What to communicate on each release

Anything that adds a permission (so admins can grant it).
Anything that adds a module (so admins can switch it on).
Anything that changes a workflow staff follow daily.
Keep it short; link to the relevant module chapter for detail.

Part 2, Training material

Capability summary (what the product does)

A one-page orientation for new users:

Bookings & schedule, Experiences (what people book), Staff, spaces & equipment (staff/spaces/equipment), the Bookings list, Calendar, day-of Check-in (staff/scan/ kiosk), Invitations & run-sheet, Customers (CRM) and Marketing.
Getting paid, Payments (your Stripe), Invoicing & quotes, Accounting export (Xero/MYOB/QuickBooks).
Your team, Team comms (announcements/chat/handover), Roster & timesheets, Shift requests, Leave, Licences & certificates, Team happiness.
Operations & compliance, Safety & cleaning, Documents, Forms & workflows, Reminders & digests, Assets & maintenance.
Food & stock, Shopping list, Recipes & menu.
Across everything, the AI assistant, Business health, and a dashboard that adapts to what you've switched on.

Core concepts to teach first

Modules, features are switched on per business; you only see what's on.
Roles & permissions, you see what your role allows.
Your wording, labels match your trade (a "booking" may be an "appointment").
Navigation, grouped top menu, notifications bell, account menu.

→ Foundations: 00 Intro · 01 Getting started · 02 Roles · 03 Dashboard & nav

Role-based learning paths

Owner / Manager (≈60 min)

Quick-start setup → a-quick-start.md
Settings, branding, wording, tools → Administrator guide
Roles & permissions → 02
Bookings end-to-end → 04
Money: Payments, Invoicing, Accounting → 14, 10, 01
Team: Roster, Leave, Shift requests, Comms → 17, 11, 19, 21
Business health, Reminders, the AI assistant → 16, 02

Supervisor (≈30 min)

Dashboard & nav → 03
Bookings, Calendar, Check-in → 04, 05
Approvals: shift requests & leave → 19, 11
Safety checks & announcements → 18, 21

Staff (≈15 min)

Logging in & the dashboard → 01, 03
Their daily tools, depending on your business: completing safety checks, using check-in, reading/acknowledging announcements & documents, the shopping list, requesting leave or a shift change, the weekly happiness check-in. → 18, 07, 20, 11, 22

Suggested hands-on exercises

Create a Live experience and take a test booking; check it in.
Raise and send a test invoice; mark it paid; export accounting.
Post a must-read announcement and confirm acknowledgement tracking.
Build the week's roster, clock a shift, approve and export timesheets.
Add an asset with a service interval; log a service.
Set up one safety checklist and complete a check with a reading.

Trainer tips

Turn on only the modules the business uses before training, so screens match reality.
Teach with the business's own wording (it's already configured).
Encourage the AI assistant as a self-serve "how do I…?" coach, it links users straight to the right screen.

Support-technician reference

Start from the Troubleshooting guide (symptom-first), then the relevant module chapter's Troubleshooting/Error-messages section.
Most "I can't see X" issues are module off or missing permission.
The nav-collapse symptom (Dashboard + Messages only) is a session desync, full sign-out/in.
Saves that fail right after a release may await a provider-side database update.

Related: README index · FAQs · Quick-start