Foundation (Day 1)

Set up the district shell so everything else has somewhere to live.

• District settings. Name the district, add your buildings or schools, and load branding. Building-level access depends on your buildings existing here, so do this first. District settings
• Team and permissions. Invite the staff who need to configure now and assign roles; you can separate access from configure per module and scope building admins to their building. Inviting your team and roles & permissions.

Roster (Day 1 to Week 1)

Get your students and staff in, and keep them current.

• Google Workspace sync (recommended). Connect the Google Directory so students and staff populate and refresh on a nightly sync. The setup walks through the Google Cloud project, service account, and domain-wide delegation. Start here.
• Grade by organizational unit. Map each Google OU to a grade so synced students carry the right grade, then clear any "No grade" gaps.
• CSV alternative. No Google, or extra fields to add? A File connector maps your columns and imports without duplicating synced people. File connector.

Devices (Week 1)

Import the fleet with the connector that matches each source. You can run several.

• Chromebooks. The Google Admin sync imports the fleet, retires deprovisioned devices, and pulls MAC addresses.
• Apple (iPad, Mac). Export from Jamf or Mosyle; the model identifier resolves to the model name and release date.
• Anything in a spreadsheet. A File connector lets you pick a match key, map columns, and review before it commits.
• Windows PCs outside your MDM. Install the Edventory Agent with an enrollment key; devices appear as they check in.
• Then add any custom fields you track and assign devices to people from the roster.

Help desks and intake (Week 1)

Open the queues that take requests and turn on the ways people reach them.

• Create your queues. One per team that takes requests, starting with IT. Creating a help desk.
• Turn on intake. A public submit form, email-to-ticket, and QR device labels that open a prefilled ticket when scanned.
• Speed tools. Save canned responses, submit on behalf of a caller, link a device and log parts, and merge duplicates.

Operations layer (Weeks 2 to 4)

Layer on the day-to-day tracking once the core is running.

• Loaner pool. A browsable pool you check devices out from and back in. Loaners.
• Licenses. Load software licenses; the list sorts by upcoming renewal and amortizes annual cost over the term. Licenses.
• Inventory and parts. Track parts and consumables and log parts used on tickets. Inventory.
• Recurring tasks. Schedule the routine work, tagged to the right help desk. Recurring tasks.

Reporting and forecasting (Weeks 2 to 4)

Turn the data into the reports and budgets your leadership asks for.

• Report builder. Drag columns into place, save and share, add charts, export to PDF, or schedule by email. Reports.
• Budget forecast and AUE. Build a multi-year refresh budget from the fleet and the Chromebook Auto Update Expiration dates. Budget forecast.

Optional modules

Enable only what the district needs; these are gated by plan or beta entitlement.

• People and facilities. HR onboarding and offboarding, Events & facilities with approval chains, and the visitor check-in kiosk.
• Staff Leave, Professional Growth, and Security Awareness / Inbox Shield are available to districts by request.

Go-live and adoption

Flip the switches that put it in front of the whole staff.

• Single sign-on. Turn on Google SSO so staff sign in without a separate password. Using SSO.
• Print and apply labels across the fleet, and publish the submit form or its QR code where staff will find it. Printing labels.
• Train the team on the two or three daily actions: file a ticket, check out a loaner, look up a device.

Ongoing

Most of this runs itself once configured: the nightly Google sync, nightly encrypted off-site backups with restore, data-retention purge, and renewal and task reminders. Production runs an always-on instance so the overnight jobs fire.