Project files, CAD/STL, code, lessons, and safety sheets

School Robotics File Hub for Teachers

The Roadrunner File Hub is a separate authenticated system for approved school partners. Ghost only explains access, routes adult requests, and links to the login after the real URL is configured.

The File Hub is a separate, authenticated system for approved school workspaces — it is not the public website. Teachers and program leads can request a workspace to share CAD/STL files, build code, lesson plans, safety sheets, and project notes with their classroom or club. Public forms on this site are adult-contact only and should never include student names, education records, or other student PII; the File Hub is where any student-adjacent content belongs, behind authentication and district approval. Before a school workspace is created, the requester confirms district approval, account ownership, retention policy, and the deletion or export workflow they'll use. File Hub access is reviewed periodically, and unused workspaces are archived to keep the system small and auditable. Email us with the school name, point of contact, and intended use to start the request.

External authenticated system

Request a school workspace

Access classroom robotics files, CAD/STL downloads, lesson PDFs, source code, safety sheets, and teacher resources through Roadrunner's separate authenticated File Hub for approved school and program partners.

Requests are reviewed by Roadrunner staff. Do not submit student names or private education records.

Teacher-managed access

What the File Hub should support

Teachers

Request a school workspace, manage student access with school approval, share build files, and archive projects at year end.

Students

Use teacher-provided credentials to access assigned CAD/STL files, code, photos, and build logs only after school approval.

Admins

Keep storage private, manage lifecycle policies, review logs, coordinate exports/deletion, and follow school data agreements.

Request Access

School workspace request

Please submit this as an adult educator, administrator, organization representative, or parent/guardian. Do not include student names, student contact information, or confidential education records.

This request goes to Roadrunner Robotics OSL staff for access review. Expected response time depends on school approval and workspace requirements.

What schools need to confirm
  • District approval for any student file storage.
  • Teacher/admin owner for accounts.
  • Retention, export, and deletion workflow.
  • No public sharing of student files by default.
  • Any required DPA, parent/guardian consent, or district policy review.

Enter the adult contact name.

Enter a valid work email address.

Enter the school, district, program, or organization.

Select your role.

Do not include student names, IDs, photos, grades, health information, or private education records.

Prefer direct email? Contact RoadrunnerRobotics.OSL@gmail.com.

Read the privacy notice

Technical details

Runbook teaser for school IT

What is the File Hub?

A separate authenticated file system for project files, curriculum, code, STL/CAD files, safety sheets, and build logs. It is not embedded inside Ghost.

Who can request a school workspace?

Adult educators, administrators, department leads, program partners, or parent/guardian contacts may request access. Student requests should go through a teacher or school admin.

How accounts should work

Teacher or school-managed accounts. Roadrunner should not collect student names through public web forms.

How files should be stored

Use private storage, school/program workspaces, revocable permissions, audit logs, backups, retention rules, and school-approved export/deletion paths.

Can students upload work?

Only after school or district approval. Do not use the public website for student uploads or student records.

Privacy disclaimer

Roadrunner does not accept student education records through this public website. File Hub workspaces should only be used after school or district approval, including any required parent/guardian consent, data protection agreement, retention rules, and deletion/export process.