Passkeys, Google sign-in and a database that enforces who sees what

In the catalogue

20 of the 218 things Muzeqo provides are explained on this page

One line each here; the full list, by group, is Everything Muzeqo provides. Each name opens its group there.

• Muzeqo AI’s key and switch — in the catalogue under Progress, lesson notes and term reports

  Every Muzeqo AI feature runs only when Muzeqo’s AI key is on the server and the school has turned on Drafts with Muzeqo AI; otherwise the app uses its own rule-based words or says that AI is unavailable, and nothing is sent anywhere.

• Bank passcodes — in the catalogue under Teacher pay

  Changing where pay goes needs a separate passcode; repeated wrong tries lock it for a while and an e-mailed reset takes effect only after a cooling-off freeze, and Stripe pays only a passcode-confirmed bank.

• Team and access — in the catalogue under Setup, import, exports and automations

  Invite admin, manager and billing staff, change roles, suspend or restore access, revoke or reissue pending invites (the invitee is reminded while it waits), all audit-logged.

• One login, many schools — in the catalogue under Setup, import, exports and automations

  A person who belongs to several schools switches between them from the header, files them into named groups on My workplaces with unread counts per school, and an owner creates another school from there.

• Row-level security per school — in the catalogue under Security and privacy

  Every query runs as the person’s database role; policies limit rows to their active school, composite foreign keys make a cross-school reference impossible to save, and staff-only columns are granted only to the tier allowed to read them.

• Roles and permissions — in the catalogue under Security and privacy

  Owner, admin, manager, billing, teacher, parent and student roles each hold a fixed permission set with per-member overrides, and a switch lets managers see finances.

• Teachers see only their students — in the catalogue under Security and privacy

  A teacher reads a student only with an active assignment or a recent or upcoming lesson, and guardian contact details only when the school allows; families see names and avatars only, never other people’s contact details.

• Append-only audit log — in the catalogue under Security and privacy

  Sensitive changes (settings, access, payouts, invoices, imports, logins, exports and more) are recorded with actor and time, filterable by date and record type, exportable as CSV, and every export is itself logged.

• Password, passkey or Google sign-in — in the catalogue under Security and privacy

  Hashed passwords, WebAuthn passkeys (Face ID, Touch ID, Windows Hello), Google sign-in once the Google client is configured (linking only verified addresses), and throttled login attempts.

• Account recovery and e-mail confirmation — in the catalogue under Security and privacy

  Forgot-password and e-mail confirmation use single-use, expiring links sent only to the account’s own address, and a security e-mail confirms every password change.

• Mobile confirmation codes — in the catalogue under Security and privacy

  One-time codes by text confirm a mobile number, hashed at rest, short-lived, with few attempts and rate-limited.

• Single-use invitation links — in the catalogue under Security and privacy

  Staff and family invitations are hashed single-use tokens with an expiry, accepted with a new password, Google or one click when signed in.

• No-access page and session continuity — in the catalogue under Security and privacy

  A signed-in person with no active school lands on a page pointing to their invite e-mail and My schools, a dead session cookie is cleared so the landing page stays reachable, and every e-mail and push link opens in the right school and portal for the reader’s role.

• Security headers — in the catalogue under Security and privacy

  Every response carries HSTS, nosniff, a strict referrer policy, camera and microphone for the site only and frame-ancestors self; only the enrolment embed may be framed.

• Upload rules — in the catalogue under Security and privacy

  Uploads are capped in size, executable types are refused, and files count against the plan’s storage without anything ever being deleted.

• Children’s privacy by design — in the catalogue under Security and privacy

  Guardians are the route for minors, there are no private teacher-to-minor chats, a child never sees the family’s money, and wherever children appear on a board it is first names only.

• Teacher checks shared with schools — in the catalogue under Security and privacy

  Built, not yet switched on: a teacher records their Working with Children Check, registration and qualifications with consent; Muzeqo staff check them against the official register by hand and record exactly what it showed (only the ABN is looked up automatically on the ABR), numbers sit in a sealed encrypted vault and are deleted on a schedule, and the teacher chooses which schools see status and expiry and reads who looked.

• Suspend and reinstate members — in the catalogue under Security and privacy

  The office suspends a membership (closing their conversations), reinstates it or changes a role, each change audited.

• Privacy policy and terms — in the catalogue under Security and privacy

  A privacy policy written to the Australian Privacy Principles that names its processors, says what is collected and for how long and how to complain, and terms that say school records belong to the school, the agreement can be ended by either side and consumer law applies; both await legal review and are kept out of search until then.

• Your records are yours — in the catalogue under From us as a company

  School records belong to the school; we process them only to provide the service, keep them separated from other schools’ data, and provide an export on request, and either side may end the agreement at any time.