Terms

Last reviewed 3 August 2026

Customer agreements control. These public terms describe baseline use of RosterBeam. An executed agreement and Statement of Work govern a school deployment and take precedence if they differ, including for licence rights, service levels, support, maintenance, fees, data handling and disengagement.

Service purpose

RosterBeam helps authorised school staff combine timetable information, support needs, staff rules and one-off changes into a proposed support-officer roster. It provides tools for review, adjustment, approval and export; it does not make the school’s staffing, safeguarding or educational decisions.

Accounts and authorised use

School applications use named identity-provider accounts, school organization membership and assigned Viewer, Planner or Admin roles. Users must protect their credentials, complete required multi-factor authentication, use only the access assigned to them and promptly report suspected account misuse.

School responsibilities

The school is responsible for deciding whether RosterBeam is approved and suitable for its intended use, maintaining accurate source data, assigning appropriate access, reviewing generated results and meeting its own privacy, records, consent, employment and safeguarding obligations. Users must not upload information they are not authorised to handle.

Human review and exports

Generated rosters can contain uncovered requirements, warnings or outcomes that need adjustment. Proposed exceptions must be decided before solving, validation errors prevent approval, and the latest revision must be approved before export. The school remains responsible for the final roster and how it is used.

Acceptable use

RosterBeam must not be used unlawfully, to infringe another party’s rights, to bypass access controls, to introduce harmful code, to probe or disrupt the service without written permission, or to process data unrelated to authorised school rostering. Public-site content and service documentation must not be copied or modified in a way that misrepresents RosterBeam.

Updates, availability and support

RosterBeam is centrally managed and may receive fixes, security updates and feature changes without action by school users. Current delivery and recovery practices are described on the Assurance page, but that page does not create an uptime target, maintenance window, support response time or service credit. Those commitments apply only when agreed in writing.

School data and service end

School data is handled as described on the Privacy page and in the customer agreement. Data return, migration assistance, retention, final deletion and disengagement support must follow the executed agreement where applicable.

Questions and concerns

Questions about use, support, privacy, security or these terms can be sent to support@rosterbeam.com. Please do not include student or staff information in an initial email.