Start
The pilot is the full district product, free, with a set end date.
A district pilot starts with a code that FlashEDU staff issue to the district’s work email. No card is taken, and the pilot does not become a paid subscription on its own. An authorized signer completes the pilot terms and the Student Data Privacy Agreement, FlashEDU creates the district workspace, and the first administrator receives an invitation. The default pilot is 30 days and 500 students, and the approved duration and student limit are shown in the invitation and on the setup page.
- The pilot runs on invoice status, not a card.
- The administrator adds the first school and either imports a roster or invites teachers.
- At the end date the district decides. Nothing converts without a signed order.
Rosters and sign-in
Rosters come from a file, Clever, or Google Classroom. Staff can sign in with your identity provider.
A district admin can import up to 2,000 students per file with name, grade, school, classroom, and teacher columns. FlashEDU is built to sync rosters from Clever, including Clever Instant Login, and from Google Classroom. A district can connect its own SAML or OIDC sign-in for staff. Students sign in with the username and password their teacher created, or by scanning a badge.
- Tell us your roster source during the review and we will confirm the sync path for it.
- Teacher-created accounts need only a name. An email in an imported file is kept only as a hash to prevent duplicate imports.
- Teachers can also be invited directly into the district workspace.
Who sees what
Two admin roles. Teachers see their own classrooms.
A district admin can do everything, including settings, billing, members, and creating schools. A school admin has every other permission, but only for the schools assigned to them. A teacher sees their own classrooms, plus read-only access to other classrooms in their school if the district leaves that default on. A district can also hide per-student detail from admin views, leaving admins with rollups only.
- Board reports and the cohort growth export are district admin only.
- Every roster, permission, and export action is written to an audit history that database triggers prevent anyone from editing or deleting.
- Admins can view and export that history, and the export is itself recorded.
What the district sets
Policy is set once at the district and only gets stricter below it.
District settings cover the Class games setting for student-versus-student play, chat, friends, cosmetics, leaderboards, AI coaching, voice practice, access to the wider consumer app, a grade-level cap on practice, allowed operations, a daily practice goal, required two-factor sign-in for staff, and the standards framework. A school or classroom can turn a feature off but never on. Teachers see those settings labelled Set by your district or Locked by your district.
- Defaults for managed students: Class games, chat, friends, AI coaching, voice practice, and consumer-app access off. Cosmetics and leaderboards on.
- A district can push assignment templates to every classroom and make them required.
- Only a district admin can change district settings. School admins can tighten school settings.
What leaders get
Rollups by school and district, a screening view, exports, and one price per student.
Admins see classroom data rolled up by school and district, a benchmark rollup across windows, and a screening view that ranks need within the district on percentile cut points the district can adjust. Exports are files for the district report, the roster, benchmark results, cohort growth, and snapshot series. The district plan starts at $999.99 a year for 500 student seats and $4.99 per student per year after that. Purchase orders and invoicing are available.
Boundary
Capture a benchmark window at the start of the pilot so the review at the end compares growth against your own baseline.

