The full district operations workspace.
The web app is the primary workspace for requests, assets, workflows, food service, reporting, admin settings, and connected-system review.
Requests, assets, student and staff workflows, facilities, food service, monitoring, reports, and district services stay connected from the main workspace to the mobile clients your teams carry through the day.
Threadhall now presents as a product family: a full web workspace, a fast iPhone companion, a spacious iPad client, and a Mac client for repeated operations work.
The web app is the primary workspace for requests, assets, workflows, food service, reporting, admin settings, and connected-system review.
The iPhone client gives staff a signed-in pocket workspace for request review, ticket follow-up, asset checks, people records, and quick operational context away from a desk.
The iPad client gives office, facilities, and leadership teams a regular-width Threadhall workspace with sidebar navigation and room to review queues, signals, and daily work.
The Mac client is built for staff who live in Threadhall all day: queue triage, request review, reporting, exports, admin settings, and cross-system operations.
Threadhall is not a generic ticket system with education words sprinkled on top. It is shaped around district records, recurring interruptions, public obligations, and the teams that have to keep moving.
Staff, students, office teams, maintenance, and food service start work through the same district front door.
Technicians and operators work from focused queues with the records, history, files, and ownership already attached.
Approved operational data can face the district: menus, status, documentation, reports, and portal services.
Leaders can see what changed without asking teams to rebuild spreadsheet summaries after the fact.
The dashboard brings requests, workflows, monitoring, cameras, backups, quick links, food service, communications, and health signals into a workspace teams can scan quickly.
The request view brings the requester, email, assignment, active work timer, related asset, attachments, private technician comments, and knowledge matches into a compact workspace.
Asset records bring together assignment, room, platform version, lifecycle, warranty, remote help status, movement history, and request history.
Food service can build menus by school year and month, manage staff meal sales and balances, and expose approved menus to the district website through the API.
Reports cover requests, assets, workflows, menus, monitoring, people, and operations trends with CSV and styled PDF output.
Student surfaces can expose school links, schedules, knowledge, and approved services without pulling staff-only operations into the student experience.
Admin settings, integrations, release controls, branding, SSO behavior, and district-specific setup live in a compact operations surface.
The refreshed gallery now spans the web workspace, Admin, iPhone, iPad, and Mac. These are product screenshots, not abstract mockups.
Threadhall keeps the operating model consistent while letting each role work from the density and device that fits the moment.
Requests, device context, knowledge, remote-help clues, and private work notes in one place.
Student changes, staff changes, people records, and approvals without inbox archaeology.
Facilities work, room context, service signals, food service, and public outputs tied together.
Live workload, inventory, food service, monitoring, and workflow reports without spreadsheet rebuilds.
The product stance is simple: keep the interface focused, keep the records connected, and give district operators the levers they need without turning every workflow into a consulting project.
Dedicated district workspaces with branded domains, role-aware access, and deployment controls.
Microsoft, Google, Synergy, Meraki, Verkada, Veeam, ParentSquare, LINQ, and local district records can all inform the same workspace.
Admin settings, release tracking, SFTP gateway sync, status checks, and implementation controls are designed for real district rollouts.
CSV exports, styled PDFs, public menu APIs, status pages, and leadership dashboards are produced from day-to-day operations.
Threadhall ships with the operational areas school teams already recognize, then lets a district tune the implementation around its own schools, roles, data, and policies.
Route tickets by department, link devices automatically, track active technician time, and keep internal notes private.
Manage assets with photos, assignment, platform versions, lifecycle, remote help state, warranties, and linked ticket history.
Create staff and student workflows that can launch Microsoft and Google account creation from the IT task tile.
Build food service menus by school year, sell staff meals, track balances, and publish menus through the API.
Watch Meraki traffic, Verkada cameras, Veeam backups, quick links, and tenant health from role-aware dashboards.
Export polished PDF and CSV reports for tickets, assets, food service balances, workflows, monitoring, and leadership reviews.
Tickets, assets, student changes, staff changes, food service menus, reports, dashboard modules, and connected-system data are easier to judge when you see them moving together.