How can we help?

Setup guides and configuration reference for Edventory. Search below, or browse by topic.

🚀

Getting started

Create your account and find your way around.

Implementation roadmap: from signup to go-live #

This is the order districts set Edventory up in, from the first sign-in to a system the whole team relies on. Work the phases top to bottom; each links to the detailed article for that step. A small district can be operational in a day and fully rolled out within a month.

🧭
The fastest path to operational is four steps: create the account, sync your roster, import your fleet, and open one help desk. Everything below builds on those. The Free tier covers up to 100 devices and 100 students, with no trial clock, so a small district can run on it indefinitely.

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 and Macs outside your MDM. Install the Edventory Agent (Windows, Mac) 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.

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.

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.

💡
One decision drives the whole timeline: whether you have Google Workspace admin access on day one. With it, roster and Chromebook import are fast and stay current on the nightly sync. Without it, budget extra time for CSV exports and manual refreshes.
WhenFocus
Day 1Account, district settings, team, roster sync started
Week 1Roster verified, devices imported, first help desk live
Weeks 2 to 4Loaners, licenses, tasks, reports, budget forecast
Month 2Optional modules, SSO, labels printed, staff trained
🤝
Want a hand? Edventory sets new districts up with you, roster and fleet included. Book a walkthrough or write to support@edventory.com.

Creating your account & first sign-in #

Edventory accounts are created one of two ways: your district is set up by an Edventory team member, or you accept an emailed invitation from your technology director. Requesting a new district through the signup form works the same way — we review every request, and when it's approved (usually within one business day) you get an email with a link to set your password.

Open your invitation

Click the link in your invitation email. It takes you to a short setup page showing your district name and role.

Choose your name and password

Enter your full name and pick a password of at least 12 characters.

Sign in

Your account is created and you're taken straight into the dashboard. Next time, sign in at /login with your email and password.

💡
Invitation links expire after 72 hours. If yours has expired, ask your technology director to send a new one from Settings → Team.

The dashboard at a glance #

The dashboard is your daily starting point. It surfaces what needs attention so the app is worth opening every morning.

  • Fleet summary — device counts by lifecycle stage, with the next end-of-life wave highlighted.
  • Ticket metrics — open tickets, opened this week, resolved this week, and average resolution time.
  • Needs attention — devices reaching end-of-life within 90 days, overdue loaners, overdue recurring tasks, and licenses renewing soon.

Navigating Edventory #

Everything is reachable from the left sidebar. What you see depends on the permissions your administrator granted you.

The main areas are Dashboard, Devices, Inventory, Loaner Pool, Licenses, Help Desks, Recurring Tasks, Activity Log, AI Forecast, Reports, and Settings. Administrators see all of them; members see only the areas they've been given.

💻

Devices

Track your whole fleet — Chromebooks, laptops, tablets, and more.

Adding a device manually #

Most districts sync devices automatically (see Google Workspace sync and Data connectors), but you can add any device by hand from Devices → + Add Device.

Add Device
Asset tag
e.g. CB-0142
Serial number
e.g. 5CD1234XYZ
Make
Dell, HP, Apple…
Model
Latitude 3120
Device type
Chromebook
Operating system
ChromeOS
Purchase date
mm / dd / yyyy
EOL / AUE date
mm / dd / yyyy
Location / label optional
Room 204 cart
Save device
Illustration of the Add Device window. Field labels match the live app.
FieldWhat to enter
Asset tagYour district's own identifier for the device (printed on the asset label).
Serial numberThe manufacturer's serial. Used to match devices during sync, so keep it accurate.
Make / ModelManufacturer and model name — powers the AI forecast's per-model pricing.
Device typeLaptop, Chromebook, iPad / Tablet, Desktop, Printer, Monitor, or Other.
EOL / AUE dateEnd-of-life, or for Chromebooks the Auto Update Expiration date. Drives lifecycle staging and budget forecasts.
StatusActive, In repair, Loaner, or Retired.
Device name, PO number, MAC addressesOptional extras: a friendly name/description, the purchase-order number, and the wired and wireless MAC addresses. All are searchable in the device table.
Assigned toWho or where the device is for (a student, room, or cart). As you type it suggests people from your team, but free text is fine too.
ℹ️
MAC address fields only accept hex digits and separators, and must be a full 6-octet address (e.g. aa:bb:cc:dd:ee:ff) to save. Google Workspace sync and file/push imports apply the same rule, so a malformed MAC from a source is dropped rather than stored.

Device custom fields #

Track the attributes your district cares about (who a device is for, how it was funded) without waiting on a new column.

Under Settings → Device fields (administrators), define your own fields: text, number, dropdown, date, checkbox, and more. Every district starts with two dropdowns you can edit: Assigned user type (Staff, Student, Lab, Network Equipment, Kiosk) and Funding source (Grant, ESSER, Perkins, E-RATE, Department).

Fill in custom fields when you add or edit a device. Dropdown fields also appear as filters in the device table, so you can answer "show me every student device" or "everything bought with ESSER funds" in a click.

Understanding lifecycle stages #

Edventory computes a lifecycle stage for every device automatically, from its age and end-of-life date. You never set the stage by hand.

StageMeaning
NewLess than a year old — recently purchased.
ActiveWithin its expected service life and healthy.
AgingApproaching end-of-life (within roughly 18 months) or past your aging threshold in years.
EOLPast its end-of-life or Chromebook AUE date — plan a replacement.
ℹ️
The aging and lifecycle thresholds are configurable per district under Settings → District → Lifecycle thresholds. See Replacement cost & lifecycle defaults.

Importing devices in bulk #

To bring in many devices at once — from a spreadsheet, an MDM export, or another system — use a Data connector rather than adding them one by one.

  • From a CSV or spreadsheet — create a File connector and map your columns to Edventory's fields. See File (CSV) import.
  • From an MDM on a schedule — create a Pull connector. See Pull connectors.
  • From your own scripts — create an API connector and push records. See API push connector.

Printing & scanning asset labels #

From the Devices page, click 🏷 Labels to download a printable PDF of asset labels — 10 per US Letter page, ready to cut (or print on 2×5 label stock) and stick on hardware.

Choose the devices

Tick checkboxes to label specific devices, or apply filters and leave everything unticked to label the whole filtered list (up to 200 per PDF).

Pick a format

QR code or Barcode (Code 128) — see below for which to choose. For QR labels, also pick where scans land: the problem-report page (default — anyone can report an issue, no sign-in) or the device record (staff only, sign-in required). Each label also prints the asset tag, model, serial number, and school in plain text.

Download & print

Click Download labels PDF and print at 100% scale (no "fit to page" shrinking) so barcodes stay crisp.

FormatHow it's read back in
QR codeScan with any phone or tablet camera. With the default problem-report link, the code opens a public "report a problem" page for that exact device (see the next article). With the device record link, it opens Edventory on that device's record (sign-in required) — and if you're signed in on another screen too, the record pops open there at the same moment, so you can scan with the phone and read on the big monitor.
Barcode (Code 128)Use a handheld USB or Bluetooth scanner — it types the asset tag like a keyboard. Click the search box on the Devices page and scan: the list filters instantly, and when exactly one device matches, the scanner's Enter keystroke opens it. The query is re-selected after each scan, so you can scan device after device without touching the keyboard.
ℹ️
No scanner hardware? The plain-text asset tag is printed on every label — type it into the Devices search box and press Enter.
⚠️
iPhone tip: scan QR labels with the regular Camera app (point and tap the yellow link), which opens Safari and keeps you signed in between scans. The Control Center Code Scanner and many third-party scanner apps open each link in an isolated in-app browser that forgets your session — making you sign in on every single scan.

QR self-service problem reports #

Every QR label printed with the default problem-report link doubles as a help desk intake point: a student or teacher scans the sticker, describes what's wrong, and a ticket is filed against that exact device — no app, no sign-in, no asset tag to copy down.

Scan the label

Any phone camera works. The page shows the device (asset tag, model, school) so the reporter knows they hit the right one.

Describe the problem

Pick a category — won't turn on, cracked screen, battery, Wi-Fi, and so on — optionally add details, and leave a name and email.

The ticket files itself

It lands in your help desk already linked to the device and school, marked with a QR source badge. The reporter gets a confirmation email with a reference number, and replies you write on the ticket go straight to their inbox.

Which help desk receives the reports? By default Edventory routes them automatically — your public help desk if you have one, otherwise your oldest active one. Districts running several desks can pick the exact destination under Settings → District → QR label reports.

ℹ️
The report page also has a footer link for staff — "Open this device in Edventory" — so the same label serves technicians and students alike.
⚠️
Labels printed before this feature shipped (or printed with the device record link) point at the sign-in flow instead. Reprint labels with the problem-report link to enable self-service reporting on those devices.

Collecting devices back in #

When devices come back — end of the year, a grade rollover, or any handed-back batch — turn on Collection mode right on the Devices page and check them in by scanning. No spreadsheets, no opening each record by hand.

Start collecting

On the Devices page, click 📥 Collect. A scan box opens with a running tally — how many you've collected, and how many devices are still assigned.

Scan each device

Scan its QR label or barcode, or type the asset tag or serial, and press Enter. Edventory clears the assignment and tells you who it came back from. The box re-focuses after every scan, so you can work straight through a cart without touching the keyboard.

Flag any damage

Leave the condition on ✓ Good for clean returns, or switch to ⚠ Damaged and add a note (cracked screen, missing keys). With Open repair ticket ticked, a damaged scan also moves the device to In repair and files a ticket automatically.

ℹ️
Scan a device that isn't currently assigned and Edventory simply says so and leaves it untouched — a stray scan never causes a wrong check-in. QR labels work too: scan the sticker and Edventory resolves the link to the right device. See Printing & scanning asset labels.

Retiring devices #

When devices leave service, retire them. A retired device leaves the active fleet, your lifecycle counts and the budget forecast, and keeps its history.

To retire one device, click Retire on its row, or open it and click Retire at the bottom of the panel.

Select the devices

On the Devices page, tick the box on each row, or the box in the header to select every row shown. Your selection stays as you search and change filters, so you can build it up in a few passes.

Click Retire

The bar above the table shows Retire N devices, where N counts the selected devices that can be retired. Click it, check the count, and confirm.

Google-managed Chromebooks are skipped, because Google Workspace sync sets their status from Google. Retire those with Deprovision instead. Devices that are already retired are skipped too, and the confirmation says how many of each it will leave alone. A building administrator retires only devices in their own school or in the district pool.

ℹ️
Retiring can be undone: open the device, click Edit device, and set its status back to Active. Every bulk retire is recorded in the Activity Log with the devices it retired.

Bulk deprovisioning #

When you retire a batch of Chromebooks, select them on the Devices page and choose Deprovision selected. You can process up to 100 at a time.

Pick a reason — same-model replacement, different-model replacement, retiring the device, or upgrade transfer. If Google Workspace sync is connected and a Deprovisioned OU is set, Edventory moves each device into that OU in Google before deprovisioning (Google locks the OU once a device is deprovisioned).

⚠️
Deprovisioning in Google is permanent and frees the Chrome Education Upgrade license. Double-check your selection before confirming.

Device Usage: why a student isn't showing #

When a grade's Reach looks low, or a student you know uses a Chromebook is missing from Device Usage, Edventory tells you why, student by student, with the fix for each.

Start from the grade

Open Devices → Usage → By grade. Under a grade's Reach, N not reporting, M filed elsewhere · see who lists the students on the roster that the row does not count, each with a reason and what to do. Not reporting students used no device in the range, so Reach plus not reporting is the whole roster; filed elsewhere students used a device, but the time is filed under another grade or school. A grade on the roster that nobody reported in still gets a row, reading 0 of N. The badges at the top count the reasons, so one common cause stands out at once.

Open a student for the full explanation

Click a student to see their roster entry, the usage in the date range and where it is filed, every device the extension checked in from, refused reports, and enrollment issues for their email domain. The same explanation is under Why isn't this counted? in a student's usage details.

Check anyone by email or name

On the Students tab, type an email or a name into Check a student. It also works for students who are inactive on the roster and for a mailbox nobody on the roster has.

Check the device

On the Devices tab, open a device. Who is checking in names the account the extension runs under (a roster student, a staff member, or someone not on the roster) and says when the student assigned to the device has not been identified on it, or checks in from a Chromebook that did not share its device ID (likely this one).

⚠️
The extension follows the signed-in user, not the Chromebook. Force-install it under Users & browsers on the org units your student accounts are in. A device can read connected, nothing recorded because a teacher's or technician's account checks in from it while the students' sessions never run the extension.
ReasonWhat it meansWhat to do
CountedThe student has usage in the range, filed under their school and grade.Nothing.
Never reached EdventoryEdventory has never heard from this account. Usually the extension is not force-installed on the student's org unit; a managed guest session or a web filter blocking edventory.com does the same.Force-install the extension on the org unit the student account is in.
Paused: Chromebook did not share its device IDThe student signed in on a school Chromebook that would not identify itself, so nothing is recorded. This happens when the student account is not in the same Google Workspace as the Chromebook (not affiliated), or the extension is not force-installed for it.Keep student accounts and Chromebooks in the same Google Workspace, and force-install the extension on the student org unit.
Connected, nothing recordedThe extension checks in, but no active time has been stored in the range. On a device, a staff account (or one not on the roster) checking in usually means the students' sessions do not run the extension.For a student: check the device is not left signed in and locked, and that its clock is right. For a staff account: force-install the extension on the students' org units.
Filed under another school or gradeThe student has usage, recorded before the roster had their grade or school: with no grade, under the Chromebook's org unit school, or not matched to them yet.Click Re-match now (Settings). Without the Configure permission there is no button: it is re-filed on its own within the hour.
No school on the rosterThe student has no school on the roster, so their usage is filed under the school of the device it came from.Set the student's school in People, or map their org unit to a school in the roster sync. Their usage then moves to it.
Counted under an earlier grade or schoolThe usage is filed under the grade or school the roster gave the student when it was recorded, for example before a promotion or a transfer. It stays there as history.Nothing. Usage from now on counts under their current grade and school.
Sign-in refusedRecent sign-ins from the student's email domain were refused (domain not on the list, auto-enroll off, or a wrong enrollment key).Follow the fix shown for the reason, usually adding the domain under Settings.
Reports refusedReports arrived but were refused, for example because of a wrong device clock or an outdated extension.Open the device for the reason.
Device not in your device listA device sent IDs that match nothing in Devices, and off-fleet tracking is off.Run the Google device sync, or add the device.
Only on a non-district computerThe account only checked in from a personal computer, and off-fleet tracking is off.Nothing, unless your policy covers personal devices.
Not heard from in this rangeThe account enrolled once but has not checked in since before the range.Widen the range, or check the extension is still on their org unit.
Not on the roster, inactive, no email, or excludedUsage is credited by email to an active roster student. Excluded accounts are never measured.Add or restore the student in People (or the roster sync), or add their school email.
ℹ️
A district Chromebook that is not in your device list yet is still measured: its time counts for the student and moves onto the device after the next Google device sync. Re-matching also runs on its own after a Google roster sync and after you add or edit someone in People. Paused accounts are left out of "accounts reporting" and counted on their own on the Overview and in Settings. A building administrator sees the students and devices of their own school.
🔄

Google Workspace sync

Pull your entire Chromebook fleet from Google Admin automatically — serial numbers, model, OU placement, AUE dates, and last check-in.

Before you begin #

Connecting Google Workspace lets Edventory import your Chromebooks — enrollment, organizational unit, AUE dates, last check-in — and read your Workspace/Chrome license seat counts. Setup is a one-time job for a Google super administrator.

You'll need:

  • Super administrator access to your Google Admin console (admin.google.com).
  • Access to the Google Cloud Console (console.cloud.google.com) to create a service account.
  • About 15 minutes. You only do this once.
ℹ️
This connects the technical-management side of Google Workspace. It does not read student or staff email, documents, or any user content — only Chrome device and license data. See Why these permissions?

Step 1 — Create a Google Cloud project & enable the APIs #

Create or pick a project

In the Google Cloud Console, create a new project (for example, "Edventory Sync") or select an existing one.

Enable the Admin SDK API

Go to APIs & Services → Library, search for Admin SDK API, and click Enable. This is what reads your Chrome device list.

Enable the Enterprise License Manager API

Back in the Library, search for Enterprise License Manager API and click Enable. This reads your license seat counts.

Step 2 — Create a service account & JSON key #

A service account is a non-human identity that Edventory uses to talk to Google on your behalf.

Create the service account

Go to IAM & Admin → Service Accounts → Create service account. Give it a clear name like edventory-sync. You can skip the optional role and access steps.

Create a JSON key

Open the new service account, go to the Keys tab, and choose Add key → Create new key → JSON. A .json file downloads to your computer — keep it safe; you'll upload it to Edventory in Step 4.

Copy the Client ID

On the service account's Details tab, copy its Unique ID (a long number, also called the OAuth client ID). You'll need it in Step 3.

🛡️
The JSON key is a credential — treat it like a password. Don't email it or commit it to a repository. Upload it directly to Edventory, then delete the local copy. You can revoke and recreate the key in Google at any time without affecting anything else.

Step 3 — Grant domain-wide delegation #

This authorizes your service account to read device and license data across your domain, using only the specific scopes below.

Open domain-wide delegation

In the Google Admin console, go to Security → Access and data control → API controls → Manage Domain-Wide Delegation.

Add the service account

Click Add new. Paste the Client ID you copied in Step 2.

Enter the OAuth scopes

In the scopes box, paste these three scopes, comma-separated, then click Authorize:

OAuth scopes
https://www.googleapis.com/auth/admin.directory.device.chromeos.readonly,
https://www.googleapis.com/auth/admin.directory.device.chromeos,
https://www.googleapis.com/auth/apps.licensing
Copy all three scopes exactly. Order doesn't matter.

Step 4 — Connect in Edventory #

Now bring it together in Settings → Google Workspace.

Settings · Google Workspace
Google admin email required
superadmin@yourdistrict.org
Service account JSON key required
Drag the .json file here, or click to paste its contents
Deprovisioned OU path optional
/Deprovisioned
Connect & run first sync
Illustration of the Google Workspace settings panel.
FieldWhat to enter
Google admin emailA Google super admin address the service account acts on behalf of. A dedicated admin account works well.
Service account JSON keyThe .json file you downloaded in Step 2. Drag it in or paste the contents.
Deprovisioned OU pathOptional. The organizational unit devices are moved to before deprovisioning, e.g. /Deprovisioned.

Click Run sync now to pull your fleet immediately. After the first connection, Edventory re-syncs automatically every night.

💡
The sync log on this panel shows each run's time, how many devices were added, updated, and deprovisioned, and whether it succeeded — a quick way to confirm everything is healthy.

Syncing students and staff from Google #

The roster sync reads your Google directory and keeps Edventory's students and staff in step with it: who they are, their building and their grade, based on the org unit (OU) each account sits in.

Add one rule per OU you want on the roster

In Settings → Google Workspace → Org-unit rules, map each OU to Student or Staff. A rule covers the OU and everything under it, and the most specific rule wins. Accounts outside every rule are left off the roster.

Name the building on each school's OU

Pick a Building on the rule for a school's OU, such as /Students/Lincoln → Lincoln High. Student OUs usually aren't the same as the Chromebook OUs your buildings came from, so without this, students synced from Google have no building.

Give per-grade OUs a grade

If students sit in grade OUs, add a rule for each with its grade, such as /Students/Lincoln/Grade 05 → grade 5. A rule with only a grade can sit under a rule with only a building.

Sync

Use Sync roster now, or Sync now when the nightly roster sync is on. The roster reloads when the sync finishes and tells you how many people were added, updated and deactivated.

ℹ️
When you move an account to another OU in Google, the next sync updates its building, grade and Student or Staff type to match. An OU with no grade keeps the grade the person already had, a staff OU clears it, and an account moved outside every rule is deactivated. People you removed from the roster by hand stay removed.

What gets synced, and why these permissions? #

Edventory requests the narrowest set of scopes that make the feature work — nothing more.

ScopeWhat it allows
…device.chromeos.readonlyRead your Chrome device list: serial, asset ID, enrollment, organizational unit, AUE date, and last activity.
…device.chromeosMove and deprovision Chrome devices — used only when you choose to deprovision from Edventory.
…apps.licensingRead seat counts for your Google Workspace for Education and Chrome Education Upgrade licenses.
…directory.user.readonlyRead your users' names, emails and org units for the roster sync.
…auth/calendar.events (optional)Add, update and remove the approved Events Edventory posts to Google Calendar. Asked for only if you turn on Google Calendar under Events → Configure.
🔒
None of the sync scopes can read user email, Drive files, or any personal content. The optional calendar scope lets Edventory see and edit events on calendars the connected account can access; Edventory uses it only to add, update and remove the events it posts to the calendars you choose. You can review or revoke the authorization any time from the same Domain-Wide Delegation screen in Google Admin.
🔌

Data connectors

Bring devices in from spreadsheets, MDMs, filtering tools, or your own scripts.

Choosing a connector type #

Connectors live under Settings → Data Connectors. There are three kinds, depending on how your data arrives.

TypeUse it when…
FileYou have a CSV or spreadsheet export to upload — a one-time or occasional import.
PullEdventory should fetch from your MDM on a schedule (currently Securly; more via custom builds).
API pushAnother system or script should send devices to Edventory automatically.
CustomNeed a pull connector for an MDM we don't support yet? We'll build it for a flat $1,000 fee.

File (CSV) import with field mapping #

Upload a spreadsheet and tell Edventory which of your columns maps to which field. The mapping is saved, so repeat imports from the same source are one click.

Create a File connector

Give it a Name (e.g. "Fall iPad import") and an optional Source label stamped onto each imported device.

Pick the match key

Under Match devices on, choose whether records are deduplicated by serial number, asset tag, or external ID. Re-imports update existing devices instead of creating duplicates.

Map your columns

Match each spreadsheet column to an Edventory field (see the field reference below). Unmapped columns are ignored.

Upload & review

Upload the file; Edventory reports how many devices were added and updated.

Pull connectors (Securly MDM) #

A pull connector signs in to your MDM and fetches devices on a schedule you choose — no manual exports.

FieldWhat to enter
MDM providerCurrently Securly.
Organization URLYour Securly organization's base URL.
API tokenAn API token generated in your MDM. Stored encrypted.
Client ID / Token URL opt.Only if your MDM uses OAuth2 client credentials.
Sync scheduleHourly, every 6 hours, daily, or manual only.
ℹ️
Credentials you enter for a connector are encrypted at rest. If a scheduled sync ever fails (for example, an expired token), the connector records the error and retries on its next cycle — it never blocks your other connectors.

API push connector #

For custom integrations, an API connector gives you a key your own systems use to push device records into Edventory.

Create the connector

Choose the API type and name it. Edventory generates an API key; copy it from the setup panel, where an admin can also reveal it again later (reveals are recorded in the activity log).

Send your devices

Your system posts device records using the key. Up to 20,000 records can be sent per request.

Rotate when needed

You can rotate the key at any time; the old key stops working immediately.

🛡️
Your API key authenticates writes to your district's data — keep it secret. If a key is ever exposed, rotate it right away from the connector's settings.

The Edventory Agent for unmanaged Windows PCs #

Windows machines that live outside Active Directory and any MDM (front-office PCs, shop computers, donated laptops) can inventory themselves with the Edventory Agent: a small installable client that reports hardware facts at every boot and once a day.

Create the connector

Settings → Connectors → New data connector → choose Edventory Agent. You get an enrollment key and a ready-made install command. Need the key again later? Open the connector's setup panel and click Reveal key — enrolling more PCs never requires generating a new one.

Install on each PC

Download EdventoryAgent.msi from the connector's setup panel, double-click it on the PC, and paste the enrollment key when the installer asks. For mass rollout, install silently with the key baked in — msiexec /i EdventoryAgent.msi ENROLLKEY=evk_… /qn — from any deployment tool, a startup script, or your standard image.

Watch devices appear

Each PC checks in within a minute of install, then at every boot and once a day (at a randomized time). The device record shows an Agent check-in section: CPU, RAM, disk & free space, BitLocker status, last user, last boot, and OS build.

QuestionAnswer
What does it send?Hardware facts only: hostname, make/model, serial, OS build, CPU, RAM, disk size/free, MAC addresses, BitLocker status, last logged-on user, last boot. No files, no browsing history, no screenshots.
Can Edventory control the PC?No. The agent is read-only by design: it sends facts and receives nothing. There is no remote-command channel.
How do I audit it?The collector is a plain PowerShell script installed at C:\Program Files\Edventory Agent — open it and read every line. Run it with -DryRun to print exactly what would be sent without sending it.
How do I remove it?Settings → Apps → Edventory Agent → Uninstall (or msiexec /x EdventoryAgent.msi /qn). The scheduled task, files, and registry entries are all removed.
Duplicate serials?Budget PCs sometimes ship placeholder BIOS serials ("To be filled by O.E.M."). The agent detects these and uses the Windows machine GUID instead, so those machines still get one record each.
ℹ️
A machine that stops checking in for 14+ days is flagged as stale in the connector panel and on its device record. That's the usual sign a PC was retired without telling anyone.
🛡️
The enrollment key can only write device records; it can't read any district data. Admins can reveal it from the connector panel at any time (each reveal is recorded in the activity log). If the key leaks, rotate it — installed agents keep the old key and stop reporting until reinstalled with the new one.

The Edventory Agent for Macs #

Macs outside your MDM (a lab iMac, a donated MacBook, an office Mac mini) can inventory themselves with the Mac version of the Edventory Agent. It reports the same facts as the Windows agent, plus FileVault status and battery wear on laptops, at every startup and once a day.

Use your agent connector

Macs use the same Edventory Agent connector and enrollment key as Windows PCs (Settings → Connectors). Open its Install & devices panel for the Mac instructions, already filled in with your key.

Install on each Mac

Copy the one-line Terminal command from the panel and run it on the Mac (it asks for an administrator password). It downloads the agent from your Edventory server, enrolls it and checks in. Or download EdventoryAgent.pkg, double-click it, and paste the key when it asks.

Deploying with Jamf, Mosyle or another MDM?

Download the configuration profile from the same panel and push it together with EdventoryAgent.pkg. The profile carries your key, so the package enrolls itself with no prompt on the Mac.

QuestionAnswer
What does it send?Hardware facts only: computer name, model and model identifier, serial number, macOS version, CPU, memory, startup-disk size and free space, Wi-Fi and Ethernet addresses, FileVault status, battery cycle count and condition, last signed-in user, last startup. No files, no browsing history, no screenshots.
Can Edventory control the Mac?No. Like the Windows agent it is read-only: it sends facts and receives nothing.
How do I audit it?The collector is a plain shell script at /Library/Application Support/Edventory Agent/edventory-agent.sh, also viewable from the connector panel. Run it with --dry-run to print exactly what would be sent without sending it.
How do I remove it?In Terminal: sudo "/Library/Application Support/Edventory Agent/uninstall.sh". The background task, files, key and log are all removed.
The package says it can't be opened?Until the package is signed by Apple, macOS asks for confirmation: right-click it, choose Open, then Open again. The Terminal install doesn't need this step.
ℹ️
The agent runs quietly in the background: after startup it waits a few minutes, and the daily check-in happens at a random time in the morning, so a lab full of Macs doesn't report all at once.

Importing from Jamf (Apple devices) #

Jamf School and Jamf Pro can export your Apple fleet as CSV. Upload that file to a File connector and map the columns.

Export from Jamf

Jamf School: Go to Devices → All, click Export, choose CSV. Jamf Pro: Go to Devices → Search Inventory, run a search for all devices, click Export.

Create a File connector in Edventory

Under Settings → Data Connectors, click + New connector. Choose File upload, name it (e.g. "Jamf iPads"), and set Match devices on to Serial number.

Map columns

Jamf columnEdventory field
Serial Numberserial_number
Asset Tagasset_tag
Modelmodel
Device Namenotes (or assigned_label)
OS Versionos
Building / Siteschool_name

Upload & review

Drop the CSV and Edventory imports the devices. Re-run monthly or whenever you want a fresh snapshot — serial-number matching prevents duplicates.

Mosyle integration: import your Apple device inventory #

Bring iPads and Macs from Mosyle Business or Mosyle Fuse into Edventory asset management: export a CSV, map the columns once, and re-run any time to keep serials, models, and OS versions in sync.

Want a live sync instead of a CSV? A native Mosyle API connector is available as a custom build for a one-time fee.

Export from Mosyle

Go to Devices, use the filter to select the device types you want, then click the Export (download) button in the top-right. Choose CSV.

Create a File connector in Edventory

Under Settings → Data Connectors, click + New connector. Choose File upload, name it (e.g. "Mosyle iPads"), and set Match devices on to Serial number.

Map columns

Mosyle columnEdventory field
Serial Numberserial_number
Asset Tagasset_tag
Device Modelmodel
Device Namenotes (or assigned_label)
OS Versionos
Tagsnotes

Upload & review

Drop the CSV to import. Re-run as needed — serial-number matching updates existing records.

Custom connector (we build it for you) #

Need a live API connector for an MDM we don't support yet? We'll build one for a flat $1,000 fee.

When you create a new connector and choose Custom integration, you tell us which system and we take it from there:

  • You provide test credentials so we can build and test against your real environment
  • We build a native pull connector — automatic scheduled sync, no manual exports
  • One-time fee, no recurring charges
ℹ️
Common requests: Jamf Pro API, Mosyle API, Microsoft Intune, FileWave, Kandji, Addigy. If it has an API, we can connect it.

Identifying Apple models (iPad, iPhone) #

Apple fleets usually import with a model identifier like iPad12,1 instead of a name you can read, and with no lifecycle dates at all. Identify model turns that into the real model name, the date Apple shipped it, and an estimated end of support.

Just need to decode one identifier? Use the free Apple model identifier lookup, no account needed.

One device

Open the device and click Identify model. It shows exactly what it will fill in before writing anything, so nothing changes until you say so.

A whole fleet

Devices → Identify Apple models does the same across every Apple device at once. It reports how many it can help with, and a sample of the changes, before applying.

It only fills blanks

Anything already recorded is left exactly as it is. Run it as often as you like — a second pass simply finds less to do.

FieldWhat you get
ModelThe real name, e.g. iPad12,1 becomes "iPad (9th generation)". A model name you typed yourself is never overwritten.
Model releasedWhen Apple started selling that model. Useful as a floor on a device's age when the purchase date was never recorded.
Est. end of supportRelease date plus the support window that family typically gets. This is what lets Apple devices appear in the budget forecast, the same way AUE does for Chromebooks.
⚠️
Purchase date is never touched. A release date is when Apple shipped the model, not when your district bought it — a 2021 iPad bought in 2024 is three years newer than its release date suggests. Writing one into the other would age the device in the forecast and ask for replacement money early, so the two are kept as separate fields.
ℹ️
End of support is an estimate, labelled as one everywhere it appears, and the forecast reports it separately from a real Chromebook AUE. If you know better, edit the device and set the EOL date yourself — your value always wins.
💡
Apple randomised serial numbers around 2021, so a serial no longer says which model it is. This works from the model identifier your MDM exported, or a recognisable model name. A device with neither is left alone rather than guessed at.

Import field reference #

These are the device fields any connector can populate. Only the match key is strictly required; everything else is optional.

FieldNotes
serial_numberManufacturer serial. Common match key.
asset_tagYour district's asset identifier.
external_idThe source system's own device ID — useful as a stable match key.
make / modelManufacturer and model name.
device_type / osType (Laptop, Chromebook, Tablet…) and operating system.
purchased_datePurchase date.
warranty_expiry / eol_dateWarranty end and end-of-life / AUE dates.
costUnit cost — feeds budget forecasts.
statusactive, repair, retired, loaner, lost, or deprovisioned.
assigned_labelFree-text location or assignment (e.g. "Grade 5 cart").
school_nameMatched to one of your schools/buildings.
notesAny additional detail.
🎫

Help desks

Run IT, Facilities, HR, and any other queue side by side.

Creating a help desk #

Every district starts with a Technology help desk. Add more — Facilities, HR, Transportation — each with its own form, statuses, and inbox.

New help desk
Name required
Facilities
Description optional
Building maintenance, HVAC, and grounds requests
Icon
🔧
Color
#5b9cf6
Create help desk
New help desks start with a standard status board: New → In Progress → Waiting on Parts → Done. You can rename, recolor, reorder, add or remove statuses later.

Custom fields #

Add fields to a help desk's form so every request captures what your team needs to act — a room number, a building, an asset tag.

SettingOptions
Field labelThe question shown on the form, e.g. "Room number".
Field typeText, Text area, Number, Dropdown, Checkbox, Date, or URL.
OptionsFor dropdowns — one choice per line.
RequiredWhether the submitter must fill it in.
Sort orderWhere the field appears on the form.

Statuses & the board #

Each help desk has its own status board. Rename, recolor, reorder, add, or remove statuses to match how your team works.

Every help desk starts with New, In Progress, Waiting on Parts and Done. Open the help desk's Configure panel and go to Statuses: Edit changes a status's name and color, the arrows change its place on the board, and + Add status adds one at the end. Tickets already in a status follow its new name straight away.

In Edit, New tickets start here picks the status new tickets land in (one per help desk, and it can't be a closed one). Deleting a status that still has tickets asks which status to move them to first. Each help desk keeps at least one closed status.

Mark a status as Closed to tell Edventory a ticket in that status is done — closed tickets drop out of your open-ticket counts and (optionally) trigger a notification to the submitter. Changing whether a status closes tickets updates the tickets already in it, including their resolution time.

When you move a ticket into a closed status, Edventory gently prompts you to add a closing note (and focuses the reply box). It's a nudge for the record, not a requirement — the status still changes either way.

Canned responses #

Save the replies your team types over and over (password reset steps, "we've ordered the part," closing notes) and drop them into any ticket in one click.

Open a help desk, expand its settings, and add canned responses under Canned responses (a title and the reply text). They're scoped to that help desk. When you're working a ticket, pick one from the Canned response dropdown in the reply box and it fills the reply for you to send or edit.

Need to tweak a saved reply? Click Edit next to it, change the title or body, and save — no need to delete and recreate it.

Filing a ticket for someone else #

When someone calls or walks up, file the ticket on their behalf so the record shows who actually has the problem.

In + New ticket, fill in On behalf of (name) and their email. That person becomes the ticket's submitter (they get the status and reply emails), while you're recorded as "Logged by" on the ticket. Leave the fields blank and the ticket is simply attributed to you.

Attaching a device & logging parts #

Tie a ticket to the device it's about, and record the parts you used to fix it.

Attach a device

On the new-ticket form or in the ticket's sidebar, search by asset tag or serial number and pick the device. You can change or remove it later from the sidebar.

Log parts used

In the ticket sidebar's Parts used section, search your inventory (or type a one-off part name), set the quantity and cost, and add it. Parts pulled from inventory draw down the on-hand count automatically; removing a part restores the stock.

💡
Parts logged here roll up into Reports → Parts used & repair spend, so you can answer "how many Chromebook screens did we go through this year, and what did they cost?"

Merging duplicate tickets #

When the same issue comes in twice (someone emails and then files the web form, or two people report one broken cart), fold the duplicate into a single ticket instead of working both.

Open the duplicate

Open the ticket you want to fold away and click Merge in its header.

Pick the ticket to keep

Search for the canonical ticket (same help desk) and confirm. Its replies, parts, and custom fields move onto the ticket you keep, repair cost is added in, and a device is adopted if the kept ticket doesn't have one.

Done

The duplicate is closed and hidden from the board, lists, and open counts, with an internal note recording the merge. You land on the canonical ticket.

ℹ️
Merging is limited to the same help desk, since statuses and custom fields are defined per help desk.

Filtering & searching tickets #

Inside a help desk, narrow the board or list to exactly what you're looking for.

  • Filter bar: dropdowns for status, assignee, and priority narrow both the board and list views; Clear filters resets them.
  • Search: the search box in the top bar filters the open help desk's tickets by title, submitter, location, or assignee as you type.

Archiving & restoring a help desk #

Deleting a help desk is reversible: it's archived, not destroyed, and every ticket is preserved.

Deleting from a help desk's settings sets it aside (its tickets are kept). To bring one back, use View archived on the Help desks grid and click Restore. (Archiving and restoring are administrator actions.)

Public web submission form #

Turn on Allow public web submissions and a help desk gets a shareable link anyone can use to file a request — no account required.

  • Post the link on your staff intranet, a poster QR code, or a help page.
  • Submitters enter their email and are notified by email as the team replies or changes status.
  • A district landing page lists all of your public help desks in one place.
ℹ️
Public forms include built-in abuse protection so they can be shared openly. You don't need to configure anything.

Inbound email (turn emails into tickets) #

Each help desk can accept tickets by email. Replies thread back onto the original ticket automatically.

OptionHow it works
Shared addressEdventory gives the help desk a ready-to-use address like yourdistrict-facilities@helpdesk.edventory.com. No DNS changes — works immediately.
Forward your own addressKeep an address staff already know (e.g. facilities@yourdistrict.org) and forward it to the unique address Edventory provides.
Display aliasOptional. A friendly address shown to submitters. It's cosmetic and doesn't affect routing.
💡
Replies are matched to the right ticket by the reference code in the subject line — so as long as people reply normally, the conversation stays on one ticket.

To pass along an email someone sent you, forward it to the help desk address. The ticket keeps your note and the whole forwarded message, from Gmail, Outlook or Apple Mail. Forwarding into a ticket that already exists (keep its reference code in the subject) adds the forwarded message to that ticket. When someone replies to a ticket, only their reply is kept: the copy of the earlier email their mail app quotes underneath is left out, so a quick "thanks" on a closed ticket stays a thank-you and doesn't reopen it. Your email signature and confidentiality footers are trimmed from your own note, never from the mail you forward.

New-ticket notifications #

Open a helpdesk, expand its settings, and add addresses under New-ticket notifications — those people get an email the moment a ticket arrives, whatever the source: the web, the public form, inbound email, or a scanned QR label.

The notification carries the title, description, submitter, and device, and its Reply-To is the submitter — a tech can answer right from the inbox. You won't be emailed about tickets you file yourself, and assignees additionally get an "assigned to you" email when a ticket lands on them.

ℹ️
Up to 10 addresses per helpdesk, comma-separated. Leave the field empty to turn notifications off for that desk.
📅

Events & facilities

Take requests to use the gym, cafeteria, or a classroom — and approve them in one place.

Setting up locations & items #

Open Events → Configure (administrators only) to define what people can request. New districts start with a sensible set — gym, cafeteria, auditorium, library, conference room, plus tables, chairs, a podium, a PA system, a projector, and trash bins — that you can rename, hide, or replace.

Locations

Add each bookable space with an optional capacity. A location is just a name you control — it isn't tied to a building or org unit, so you can list anything from "Main Gym" to "Room 204". Optionally give a location its own approver and coordinator email to route that building's requests to the right person; leave them blank to use the district-wide pair.

Items

Add the gear a requester can ask for. Flag an item as having a quantity (tables, chairs) and requesters enter how many; leave it off for one-offs like a podium or microphone.

Hide instead of delete

Toggle a location or item to Hidden to retire it from new requests without erasing the ones that already reference it.

Submitting & approving a request #

From Events → + New request, staff pick a location, the date and time, expected attendance, and check off the items they need. Requests land as Pending for a coordinator to review.

Open any request to see the details, then Approve or Deny with an optional note to the requester. If another request already overlaps that location and time, Edventory shows an overlap warning on the request — it never blocks you, so you stay in control of double-bookings (a setup-and-teardown overlap is sometimes exactly what you want).

ℹ️
When a request arrives it goes to the location's approver if one is set, otherwise the district-wide approver, otherwise everyone with Events access. The requester is emailed an acknowledgement on submit and again the moment you approve or deny; on approval the location's coordinator (or the district coordinator) is notified too — times are shown in your district's timezone (set it under Events → Configure).

Drawing a room layout #

Every request includes an optional room layout — a drag-to-draw grid for sketching exactly how the space should be set up.

Pick a tool — chair, round table, or rectangular table — then click or drag across the grid to place them; the eraser removes a cell and Clear all starts over. The finished diagram is saved with the request and shown to whoever reviews it, so your setup crew sees the arrangement at a glance instead of decoding a paragraph of instructions.

ℹ️
The layout is optional — skip it and the typed Setup instructions field works on its own.

Posting approved events to Google Calendar #

Edventory can put every approved event on a Google Calendar the moment it's approved, and take it off again if it's denied, cancelled or deleted.

Connect Google Workspace

An administrator connects Google Workspace under Settings → Google Workspace, if it isn't already. In the Google Cloud project behind that connection, turn on the Google Calendar API (APIs & Services → Library). Calendar access is a separate permission: with the OAuth connection, click Grant calendar access under Events → Configure; with a service account, open the Google Admin console's Security → Access and data control → API controls → Manage Domain Wide Delegation, edit the entry for the service account's client ID (Events → Configure shows it), add https://www.googleapis.com/auth/calendar.events to its OAuth scopes while keeping the ones already there, and click Authorize. Copy full scope list copies everything Edventory uses, ready to paste over the whole box.

Choose the calendar

In Google Calendar, open the calendar's settings, copy the Calendar ID under Integrate calendar, and share the calendar with the connected Google account using Make changes to events. Paste the ID under Events → Configure → Google Calendar and save. Edventory checks it can add events there before saving.

Per-room calendars (optional)

To send a room's events to its own calendar, such as a Google room resource calendar, add that calendar to the location under Locations. Locations without one use the district calendar.

Turn it on

Check Post approved events to Google Calendar. Upcoming approved events go up right away; from then on every approval is posted as it happens.

Choosing the account that adds the events

Events are added as the Google Workspace connection's account unless an administrator picks another, such as a dedicated events account. The Google Workspace connection, and your device and roster sync, stay as they are.

  • Service account: under Events → Configure, click Change next to the account and enter any user in your Google Workspace. The service account acts as that user for the calendar only, using the same domain-wide delegation, so nothing else needs adding in the Admin console. It has to be a user account that can sign in (a person, or a shared account), in your own domain, with Google Calendar turned on for its organizational unit. A Google Group or an alias won't work.
  • OAuth connection: click Use a different Google account and sign in as that account. Google asks it only for calendar access.

Share every calendar Edventory posts to with the new account using Make changes to events before switching. Edventory checks them first, and a service-account change isn't saved until they all pass. Events already on the calendar keep their original creator, because Google doesn't let that change, but the new account updates and removes them from then on. Use the Google Workspace account switches back.

Each calendar event shows the title, location, start and end, the description and the requesting organization (or the requester's name when no organization is given). It never includes the requester's email, phone, attendance or setup notes.

ℹ️
If Google can't be reached, or the calendar isn't shared with the right account, the event shows Couldn't update Google Calendar with the reason, and Edventory keeps trying. Fix the cause, then use Sync now or Try again now on the event. Turning the feature off takes the upcoming events Edventory added off the calendar; past events stay.

The public request link #

To let PTAs, booster clubs, and community groups request space without an account, turn on the public link under Events → Configure and share the URL it gives you.

The public form shows your district name and the same locations and items as the staff form, and submissions arrive in your Pending queue marked Public link so you can tell them apart. The form is protected by rate limiting and a spam honeypot, and it's off until you enable it.

🪪

Visitor check-in / check-out

Log who comes through the door, who they're visiting, and when they left.

Checking a visitor in #

Open Visitors → Check In and fill in the visitor's name, who they're visiting, and their purpose. When you've seen their ID, tick ID verified and choose the document type — the record stores that a check was done, not the ID number itself.

Required fields

Visitor name and Visiting (host name) are required. Everything else — company, purpose, ID verification, badge number, and notes — is optional.

Purpose options

Choose from Meeting, Volunteer, Vendor/Contractor, Parent/Guardian, Interview, Delivery, or Other. This helps you filter the log later.

Badge number

If your school issues visitor badges, record the badge number in the form — it appears in the active visitors list so staff know which badge to collect at the door.

Checking a visitor out #

Every active visitor in the Currently checked in panel has a Check Out button. Clicking it timestamps the departure and moves the record to the log — you'll see the visit duration automatically.

A visitor who never checks out is closed automatically at midnight and shows in the log as Not signed out, with no visit length. You can export the log to CSV at any time from Visitors → Log → Export CSV.

ℹ️
Visitor records are kept permanently — they are not subject to the 90-day analytics purge — so your log stays intact for compliance, incident review, or records requests.

Searching and exporting the log #

Switch to the Log tab to search all past visits. The search box matches visitor name, company, host, purpose, ID type, badge number, and notes.

To see one day, pick it in From. Add a To date to see a range, or set only To to see everything up to that day. The line under the title confirms what you're looking at, for example "42 visits on Oct 6, 2026". Days and times follow your district's time zone, so a visit at 11:30 PM stays on the day it happened. Clear resets the search and dates.

The log shows 100 visits at a time, newest first, with a count of every match and Prev / Next to page through them. Export CSV downloads every visit matching the search and dates, not just the page on screen, with the date, visit times, length, ID check, badge, purpose, and notes. Administrators can also delete individual records from the log.

👥

Team & permissions

Invite staff and control exactly what each person can see.

Inviting a team member #

From Settings → Team → + Invite, enter an email and choose what the person can access. They get an email link to set up their account. If it lands in spam or goes stale, hit Resend next to the pending invite — same link, fresh 72-hour expiry.

Invite team member
Email required
teacher@yourdistrict.org
Administrator
Full access to everything, including team management
Area access (for members)
Dashboard Devices Inventory Loaner Pool Licenses Help Desks Recurring Tasks Activity Log AI Forecast
Send invite
Illustration of the invite window with per-area permissions.

Roles & granular permissions #

There are two levels of access.

RoleAccess
AdministratorFull access to every area, plus team management, billing, and district settings. (This is the technology-director role.)
MemberAccess only to the areas you switch on — Dashboard, Devices, Inventory, Loaner Pool, Licenses, Help Desks, Recurring Tasks, Activity Log, AI Forecast.

For help desks, you can grant access to all help desks or pick specific ones — so a Facilities lead sees only the Facilities queue. Members can also be scoped to a single school or building.

Every member can always reach Settings → Account to manage their own password, two-factor, and theme.

Resetting a member's password or two-factor #

When a staff member is locked out, an administrator can help from the Team panel — no need to contact support.

  • Reset password — sends the member a secure link to choose a new password. The link expires in one hour. You never see or set their password yourself.
  • Reset 2FA — clears two-factor on a member who lost their authenticator and backup codes, letting them sign in with their password and set it up again. This button only appears for members who currently have 2FA on.
🧑‍💼

Onboarding & offboarding

Run the same checklist for every new hire and every departure — with the position-specific extras built in.

How onboarding & offboarding checklists work #

Onboarding in Edventory is built around positions, not people. You write the checklist once for "Music Teacher" or "Bus Driver", then start one every time you fill that job. Two words, two things: a checklist is the reusable list of steps; the live copy you're working through for one person is that person's onboarding (or offboarding). The Onboarding view in the sidebar's HR section holds three tabs: In progress, Completed, and Checklists.

Checklists are the templates

A checklist is a reusable list of steps for one process — onboarding or offboarding — belonging to one position. Nothing on a checklist is tied to a person or a date; steps are stored as an offset like "5 days before" or "on the first day".

An onboarding is the live copy

+ Onboard someone (or + Offboard someone) takes a snapshot of a checklist's steps, turns each offset into a real due date from the date you enter, and tracks the tick-boxes. Editing the checklist afterwards never disturbs one already under way — and working through one never changes the checklist.

Phases keep it readable

Every step sits in one of four phases — Before start day, First day, First week, First month (an offboarding checklist reads Before last day, Last day, First week after, Wrap-up). The run view groups the tasks under those headings and shows a progress bar.

ℹ️
Onboarding lives alongside Staff Leave under the sidebar's HR heading. It's rolled out district by district — if you don't see it, ask us to turn it on for your district.

The base checklist and position variations #

Most of what you do for a new hire is the same regardless of the job: create the account, order the laptop, add them to the phone list. Put those steps on the base checklist, and every position checklist picks them up automatically.

Create the base first

Checklists → + New checklist, name it something like "All new staff", and tick This is the base checklist. You get one base per process — one for onboarding, one for offboarding.

Then add positions

Create a checklist per position that needs something extra — "Music Teacher", "Bus Driver", "Building Secretary". Leave the base box unticked and it inherits every base step, marked inherited in the editor.

Edit the base once, everywhere updates

Add a step to the base and it appears on every position checklist immediately — including the ones you wrote months ago. That's the point of the split: shared steps have exactly one home.

BadgeWhat it means
inheritedComes from the base checklist and still tracks it. Change it on the base and this position follows.
customizedAn inherited step this position edited. It has forked — later base edits no longer reach it until you reset it.
addedA step that exists only on this position.
💡
No base checklist yet? A position checklist works fine on its own — it just carries all its own steps. You can create the base later and the positions you already wrote will start inheriting from it.

Customizing a position's steps #

Open a position checklist and every step is editable in place, whether it came from the base or not. Editing an inherited step doesn't touch the base — it makes this position's own copy.

Change an inherited step

Hover the step and click Edit. The dialog warns you that the change applies to this position only. Rewrite the title, move it to a different phase, shift the due offset, or point it at a different person. It now reads customized.

Undo a customization

Click Reset on a customized step to throw away the fork and go back to the base version — including any base edits made while it was forked.

Skip a step this position doesn't need

Click ✕ on an inherited step. It disappears from this position only; the base keeps it and other positions still get it. Reset brings it back.

Add position-only steps

+ Add task writes a step that belongs to this checklist alone — "issue instrument locker key", "order an audio interface".

Start from a similar position

Duplicate copies a checklist, customizations and all, under a new name. Handy when two positions differ by a step or two.

Rename it later

Job titles change. Rename retitles a checklist in place, keeping its steps, its customizations, and the positions that inherit from it. Checklists already running keep the title they started under, so a finished onboarding still says what the job was called at the time.

FieldWhat to enter
TaskWhat has to happen, written as an instruction — "Create Google account", "Collect classroom keys".
PhaseWhich stage it belongs to. Drives the grouping and the default ordering.
DueDays from the start date. 0 is the start date itself, −5 is five days before, 14 is two weeks after.
AssigneeThe team member responsible. They get an email when the checklist starts, and a nudge when the task goes overdue. Leave it unassigned to decide per hire.
Can't start until…Holds this step locked until every step above it is done. See Putting steps in order.
NotesAnything the assignee needs — the OU to place them in, which cart the loaner comes from.

Putting steps in order & making one wait for another #

Some steps genuinely can't start until earlier ones land — you can't create the Google account before the hire is even approved. Order the list the way the work actually happens, then tick Can't start until the steps above it are done on the ones that have to wait.

Put the list in order

Drag a step by its ⠿ grip to move it. Drag it under a different phase heading and it moves to that phase. No mouse? Tab to the grip and use ↑ / ↓ — same result, and your place in the list is kept.

Mark what has to wait

Edit a step and tick the box. It now shows ⛓ waits on the checklist, and on a live run it stays locked — greyed out, with its tick-box disabled — until every step above it is done or skipped. It says how many it's still waiting on.

Let the rest run in parallel

Leave the box unticked on anything that can happen any time — ordering the laptop, the badge photo. Only the steps you gate wait, so a checklist doesn't turn into a single-file queue.

The handoff

The moment the last step above it is ticked off, the gated step unlocks and its assignee is emailed that it's their turn. Whoever ticked the box sees who's up next.

💡
Worked example. Order the steps Interview → Hire approved → Payroll paperwork → Create Google account, and gate only the last one. IT hears nothing while HR works through the first three; the day paperwork clears, the account request lands in their inbox.
ℹ️
Reordering a step on a position checklist changes the order for that position only, so that step becomes customized — the steps around it keep tracking the base. Reorder on the base checklist and every position follows.

Onboarding or offboarding someone #

Click + Onboard someone or + Offboard someone, pick the position's checklist, name the person, and set the date. Edventory copies the resolved steps — base plus this position's variations — and turns every offset into a real due date.

Pick who it's for — or don't, yet

Type a name, or search your roster to link it to a real person. Linking matters for offboarding (see below) and fills the name in for you. The field is optional: start the paperwork for a post you haven't filled and it simply reads "no name yet" until you know. Edit details on the record puts the name in whenever the offer is accepted.

Set the date

The Start date (or Last day, offboarding) anchors every due date. Change it later under Edit details and every still-open task shifts by the same number of days — which is what you want when a start date slips.

See who owns what

Every step carries its assignee's name in their own colour, and the chips above the list show each person with how many steps they still have open. Click one to narrow the list to just that person's work.

Work the list

Tick tasks off as they're done; the progress bar and the In progress row update. Tick the last one and the run moves to Completed and emails everyone who worked on it. Un-tick a task on a finished run and it comes back to In progress.

Adjust it as you go

It's a copy, so you can edit it freely: Edit details for the name, date or notes, + Add task for the one-off that came up, Edit on a step to reassign or move a due date, ✕ to drop one that doesn't apply to this hire. None of it touches the checklist.

ℹ️
Each one keeps the position name it started under. Rename or delete the checklist afterwards and anything already in flight is unaffected — so a finished onboarding still records what the job was called at the time.

Offboarding: collecting devices, loaners, and seats #

The gear a departing employee is holding is already in Edventory, so an offboarding run doesn't make you look it up. Link the run to a person from your roster and Edventory adds a collection task for every device assigned to them, every loaner they still have out, and every license seat in their name.

Preview before you start

Choose an offboarding checklist and pick the person, and the dialog lists exactly what will be added — "3 collection tasks will be added from what they currently hold: CB-0421, HP-1180 (loan), Adobe Creative Cloud (seat)". Nothing assigned? It says so.

The tasks arrive tagged

Collection tasks appear in the run marked from inventory, alongside the checklist's own steps. They're normal tasks from there — assign them, re-date them, or delete one that doesn't apply.

Ticking them off isn't a check-in

Marking a collection task done records that the item came back on the checklist. Actually returning the loaner or reassigning the device still happens on the device record or in the loaner pool, so your inventory stays the single source of truth.

💡
License seats are matched on the person's email address, so keep roster emails accurate — that's how a seat gets tied back to the human who's leaving.

Who gets emailed, and when #

Onboarding usually spans several people — IT builds the account, the office does payroll paperwork, a building admin hands over keys. Edventory emails each of them their own slice rather than copying everyone on everything.

WhenWho hears about it
A checklist startsEvery assignee gets one digest listing only their tasks, with due dates. Nobody gets a message for the tasks you kept for yourself.
A task is assigned laterJust that person, with the task and its due date. Assigning something to yourself sends nothing.
A gated step unlocksIts assignee, the moment the last step above it is done — "it's your turn". This is the handoff, so they aren't told about it on day one when they couldn't act anyway.
A task goes overdueOne nudge per assignee per day, listing everything of theirs that's past due across all their runs. Ticking it off in time means no email at all — and a step that's still waiting on earlier ones is never nagged about.
The run finishesEveryone who was assigned a task on it, plus whoever started it.

Need to chase people mid-run? ✉ Re-send assignments on the run re-sends each assignee their open tasks, and tells you how many people it reached.

Several steps in a row go out as one email

Checklists usually hand work over in stretches: the office does the paperwork, then IT does four things in a row, then the principal signs off. When the first of those four unlocks, IT gets one email listing all four — not one email now and another every time they finish a step. They can see the whole handoff, start at the top, and work down without their inbox filling up behind them.

A stretch ends as soon as a step belongs to someone else. If IT owns two steps, then the principal owns one, then IT owns another, that's two separate handoffs to IT, and they hear about each one when it comes round.

Turning email off for a single step

Some steps are their own notification — you're standing next to the new hire while they sign the handbook. Untick Email the assignee about this step when you add or edit it, and that step goes quiet: no start digest entry, no "assigned to you", no "your turn", no overdue nudge. Steps set this way show a small no email tag in the checklist.

It only affects email. The step still appears in the checklist, still has to be ticked off, still keeps its place in the order, and still holds back any step gated behind it.

ℹ️
Turning email off for one step never silences the steps after it. If a quiet step is the first in someone's stretch, the next step of theirs that does send email becomes the one that announces the handoff.
ℹ️
Reminders only go to team members with an Edventory login. A step assigned to nobody never emails anyone — it still shows in the run as unassigned so it doesn't get lost.

Who can see and edit checklists #

Onboarding is a permission like any other feature area, with a second level for the people who own the process. Grant them under Team → a member → Permissions.

  • Onboarding — see the runs and checklists, tick tasks off, and add or edit tasks on a live run. This is what most of the team needs: they're doing the work, not designing the process.
  • ⚙ Edit checklists — additionally create, edit, duplicate, and delete the checklists themselves. Reserve it for whoever owns onboarding, so a well-meaning edit to the base doesn't reshape every position at once.

Administrators have both. Nobody without the Onboarding permission sees the sidebar entry at all.

ℹ️
Deleting the base checklist is refused while position checklists still inherit from it — unlink or delete those first, so no position is left pointing at a checklist that's gone.
🎓

Staff Development

PD requests with principal approval, individual plans and goals, your own catalog of trainings, college courses and endorsements.

How Staff Development works #

Staff Development (formerly Professional Growth) is where teachers ask to attend professional development (PD), plan their own growth, and keep a record of what they did. Principals approve, and the district office pays and reports.

Teachers

Teachers sign in with Google. Anyone active on your staff roster can, and their sign-in only opens Staff Development. On My PD they write an Individual Professional Development Plan (IPDP), file requests with + New request, track endorsements and keep a private file cabinet of certificates and transcripts. The Catalog lists the trainings your district hosts.

Principals

Each school's principal approves its teachers' requests and plans, by a link in an email or in the app. A principal doesn't need an Edventory account to approve by email, and one who is a Staff Development manager (access with Configure on) and whose Team account belongs to the school sees what is waiting for them under Review.

The district office

Staff Development managers set things up in Settings, check completions, record payments, and follow everyone's hours on the Educators tab. All requests lists every request with filters for status, who pays and college courses.

StageWhat it means
Prior approvalSent to the principal. The teacher can still edit or withdraw it.
ApprovedThe teacher attends, then turns in the Completion: proof, hours and, when they paid, a receipt. A completion sent back for changes stays here.
PaymentThe district office accepted the completion and pays the vendor or reimburses the teacher. A no-cost activity is done once its completion is accepted.
ℹ️
Staff Development is turned on district by district. If you don't see it in the sidebar, ask us to turn it on. Give a Team member Staff Development access, with Configure on, to make them a Staff Development manager. Each tab has its own link, such as #pd/review, that you can bookmark or share.

Setting up Staff Development #

Managers set everything up on the Settings tab of Staff Development. Start with the Principals table: it decides where requests and plans go.

SettingWhat it does
PrincipalsOne row per school: the principal's email, a yearly college budget, and the one school goal everyone at the school works toward this school year (one or two sentences). Each school's street address, under Settings → District, is where teachers' mileage starts.
District approversA primary and an optional backup who approve requests from schools with no principal email, and from staff with no school. Both get the same link, and the first decision counts.
Annual hours targetThe PD hours each teacher should earn per school year. The Educators report flags anyone below it. Use 0 for no set requirement.
Mileage rateWhat the district pays per mile, for example the IRS rate. Leave it blank to track miles without a dollar amount.
Course typesThe activity types teachers choose from, such as Conference or Workshop. Tick College course on a type to ask for the college fields and count it against the school's college budget.
Budget codesYour funding lines, such as a Title II-A grant. Teachers can suggest one, and the business office confirms it when it accepts the completion.
District goalsDistrict-wide priorities. A catalog session can support one, and so can a request from a teacher whose school has no goal of its own.

Who approves

A request goes to the principal of the teacher's school. With no principal email it goes to the district approvers, and with neither, a Staff Development manager decides it in the app. Nobody approves their own request, and nobody accepts or pays their own completion, district managers included. A principal's own request (or plan) goes to the district approvers, and another Staff Development manager decides a manager's own request.

Principals in the app

A Staff Development manager whose Team account belongs to a school acts as that school's principal. They decide its requests and plans, set its college budget and school goal, and manage the catalog sessions their school hosts. They can delete their school's requests that were never approved. District settings, completion review, payment, district-wide sessions and anything already approved or paid stay with managers who cover the whole district.

Hiding schools you don't use

The Google Workspace sync makes a school for every device OU it finds, so the Principals table can fill up with carts, labs and grade levels. A district-wide manager clicks Hide on a row to move it into the collapsed Hidden from Staff Development group at the bottom, or Hide N schools with no staff to tidy them all at once. A hidden school stays in Edventory for devices, loaners and the roster, its staff still show in reports, and past requests keep its name. It's only left out of Staff Development's school lists. Clear its principal email, college budget and goal first, and click Show to bring it back.

Extra approval steps

Need a curriculum director to sign off too? Add steps after the principal under Advanced: extra approval steps. Each step is emailed in turn once the one before it approves.

Requesting PD: costs, mileage and who pays #

From My PD → + New request, a teacher fills in a short form that only asks for what applies, then sends it for approval.

FieldWhat to enter
What is it?The name of the conference, workshop or course, with its type, provider and dates.
WhereThe venue's street address. It is also where mileage ends.
Planned hoursShown to the principal, and filled in for you when you turn in the Completion.
Counts towardGraduate credit, Recertification hours, Mentor hours or Mentee hours. Reports total each one separately.
Who paysDistrict pays (PO or vendor), Reimburse me (you pay, then turn in a receipt), or No cost.
Costs & travelRegistration or tuition, lodging for an overnight stay (nights optional), mileage, and other costs such as parking. Edventory adds them up for the estimated cost.

Mileage

Tick I'm driving. The start address is your school's and the end address is the venue's; change either one if you need to. Where Edventory can look up driving distances, Calculate miles fills in the one-way miles from Google Maps. Otherwise, or if you prefer, type the one-way miles yourself.

Always a round trip

Edventory doubles the one-way miles and prices them at your district's mileage rate, for example "12.4 mi each way x 2 = 24.8 mi round trip, $17.36 at $0.70/mi".

Supports

"Supports our school goal" is checked for you. You can also pick one of your plan goals, so the activity counts toward that goal's progress.

💡
You can edit a request until an approver signs off, and withdraw it if plans change. The request shows a three-step bar, Prior approval, Approved and Payment, so you always know where it is.

Approvals, Completion and payment #

Every outside activity needs approval before the teacher attends, including college courses. Trainings from your own catalog don't.

The principal decides

The principal gets an email with the request, its costs and, for a college course, the school's college budget. Approve or Deny works from the email link with an optional note. A principal who is a Staff Development manager and whose Team account belongs to the school can also decide under Review → Needs your action.

Managers keep it moving

Review is split into Needs your action and Waiting on principal, with a count next to Staff Development in the sidebar. A district manager can resend the approval email, or decide for the principal. Edventory warns first when that skips approval steps.

The teacher turns in the Completion

After attending, the teacher opens the request and works down a checklist: proof of completion (a certificate, or a transcript and grade for a college course), the hours or credits earned, a receipt and the amount when they are being reimbursed, and a short reflection when the activity supports one of their plan goals. Submit completion turns on when everything is there.

The district office accepts and pays

A district manager checks the completion and either accepts it, confirming the amount and budget code, or sends it back with a note. Then Mark reimbursed records the check with its date and reference. A district-pays request can be marked paid, with a PO number, as soon as it is approved.

ℹ️
The business office can change who pays until the completion is accepted. Every decision, completion and payment is in the Activity Log.

Writing an IPDP with SMARTC goals #

An Individual Professional Development Plan (IPDP) sets one to three goals for one to three school years. The teacher writes it once and the principal approves it once.

Start your plan

On My PD, click Start your plan, pick the school year it starts and the one it ends, and write up to three goals. Save draft keeps your work; Submit to my principal sends it, or lists what is still missing.

A two-sentence summary

Each goal starts with a summary of one or two sentences, up to 400 characters. It is how the goal shows everywhere, so keep it short. Edventory warns you past two sentences but never stops you.

Six SMARTC lines

Below the summary, one line each: what you will do, how you will measure it, the support you need, why it matters, when, and who you will work with.

Approval

The plan goes to your principal like a request does. They approve it, or send it back with a note on what to change. An approved plan's goals are locked. Saving a change sends the plan back to draft, and it needs approving again. Close the editor without saving to keep your approval.

Track your progress

Each goal lists the requests and catalog sessions that support it, with the hours and credits they earned. Add a + Progress note, with a document from your file cabinet if you like, and Mark met or Drop goal when the time comes. A dropped goal can be made active again if it was part of the plan your principal approved; one dropped before that is added back by editing the plan.

SMARTCThe question it answers
SpecificWhat exactly will you do?
MeasurableHow will you know it worked? What will you measure?
AchievableWhat will you need to reach it (time, training, materials)?
RelevantHow does it help your students or our school goal?
Time-boundBy when, and what are the checkpoints along the way?
CollaborativeWho will you work with, and how?

The catalog: your own trainings and series #

The Catalog lists the trainings your district hosts. Teachers register themselves, with no approval needed, and can link the session to their school goal or one of their plan goals as they do. The hours land on their record once attendance is taken.

Add a session

Managers click + New session and give it a name, a host school and room, the date and time, the PD hours, the number of seats, a facilitator, what it counts toward, and the goal it supports. Its address defaults to the host school's. A principal adds sessions for their own school, and manages only those.

Group sessions into a series

Pick a series, or start a new one, on each session. The Catalog shows a series' sessions together, numbered "Session 2 of 4". A principal renames and adds sessions to a series only when their school hosts every session of it; a district manager handles a series that spans schools.

Register for the whole series

Teachers can register for every upcoming session of a series in one step. If a session they are not in yet is full, nothing is registered and the Catalog names the full session, so they can sign up for the others one at a time. Leave series cancels only the sessions that haven't started.

Take attendance

After each session, open Attendance on its card and tick who came. Attendees earn the session's hours and can print a certificate. Attendance and hours stay with each session, even in a series.

College courses and the college budget #

Choosing a college course type on a request asks for the college or university, course number, semester or term, and planned credits, and checks the request against the school's college budget.

  • A budget per school. Set each school's yearly college budget in Settings → Principals. A school year runs July 1 to June 30, and a summer course counts in the school year it ends in.
  • What counts as used. The school's college courses this school year, from the moment they are approved. Each counts at its estimated cost until the business office approves an amount.
  • Warns, never blocks. The form, the principal's approval email and the spending report all say how much is used and what this request leaves, or how far over it goes. The principal still decides.
  • Completing it. The teacher turns in a transcript and the grade, along with the credits earned.
💡
Tick College courses on the All requests tab to see only college courses. The Educators tab's Spending card shows each school's budget, what is used and what remains.

Tracking endorsements #

Teachers keep their endorsements on My PD → My endorsements: the ones they hold and the ones they are working toward.

Add an endorsement

Click + Add endorsement and give its name, its status, Held or Pursuing, the date it expires, and any notes, such as what renewal needs.

Count activities toward it

On a request, pick it under Counts toward endorsement. Each endorsement adds up the hours and credits of the activities behind it once their completion is accepted.

See what expires soon

Managers find Endorsements expiring on the Educators tab: held endorsements that run out this school year or next, with the ones already past marked Expired, a school filter and a CSV export. A principal sees their own school.

🔁

Loaner pool

Check devices out, track condition, and see what's due back.

Checking a device out & back in #

From Loaner Pool → + Check Out, look up the device and record who has it and when it's due.

FieldWhat to enter
DeviceThe loaner's asset tag or serial.
Checked out toFree text — a person, room, or cart (e.g. "Room 204", "Grade 3 cart").
Due dateWhen it should come back. Overdue loaners surface on the dashboard.
Condition outExcellent, Good, Fair, or Poor — compare against condition on return to flag damage.

When the device returns, check it back in and note its condition. Returned loaners stay in the history for the record.

Naming loaners: Loaner 1, Loaner 2 #

Give each loaner a short name that matches the sticker on it, so staff can find Loaner 7 at a glance instead of reading serial numbers.

Name them as you add them

In Loaner Pool → + Add to pool, the Loaner name field starts one past the highest Loaner number in use. Pick a device and the name moves on to the next one, so you can add a whole cart in a row. To reuse a freed name, such as a retired Loaner 4, type it over the suggestion.

Or number the ones you already have

Name unnamed loaners gives every loaner without a name the next Loaner number, in asset tag order. Use Rename on any row to change one.

Check out by name

Click Check out on the loaner's row. The window is titled with its name and the cursor is already in Checked out to: type the person, room or cart and press Enter. If what you typed is exactly one person's name on your roster, the loan is linked to them; anything else is saved as typed. To pick from the suggestions instead, click one.

ℹ️
A name stays tied to its device's serial number and shows on the On loan list and in loan history, where you can search by it. Each name is used once in your district. Removing a device from the pool frees its name for another device.

Back-dating dates & fixing a loan #

Logging a checkout that already happened, or correcting a mistake after the fact? You don't have to return and re-check-out.

  • Checkout date: set it to a past date when you're recording a loan after the fact (it defaults to today). A future date isn't allowed.
  • Return date: when checking a device back in, you can back-date the return. It can't be in the future or before the checkout date.
  • Edit a loan: click Edit on an active loan to correct the borrower, due date, checkout date, condition, or notes in place.
ℹ️
The "Checked out to" field suggests people from your team as you type, but still accepts free text like a room or cart.
🔑

Licenses

Track software subscriptions, seats, and renewal dates.

Adding & tracking licenses #

Record software renewals, firewall subscriptions, and seat-based licenses so nothing lapses unexpectedly. Add them under Licenses → + Add License, or let Google Workspace sync import your Google seat counts automatically.

FieldNotes
Product nameRequired, e.g. "Microsoft 365 A3".
VendorWho you buy it from.
License typeSubscription, perpetual, concurrent, site, and so on.
Seats total / assignedPowers utilization tracking, so you can spot licenses you're over- or under-buying.
Annual costFeeds the budget forecast.
Renewal dateReminders are emailed 60, 30, and 15 days ahead.
Auto-renewsFlag whether it renews on its own.

Open a license to edit it and you'll find a Seat roster: add the people who hold a seat, either by searching your team or typing a name and email. For licenses you track by hand, the assigned-seat count follows the roster automatically; Google-synced licenses keep the seat count from the directory.

The seat fields stay editable on every license type (including subscriptions), and a value of 0 is kept as 0, so your seat counts won't silently disappear when you reopen a license to edit it.

📋

Inventory

Count the cables, chargers, adapters, and parts.

Tracking supplies & parts #

Inventory is for the countable items that aren't tracked individually — cables, chargers, hubs, repair parts. Add items under Inventory → + Add Item.

FieldNotes
Namee.g. "USB-C chargers".
CategoryA grouping like "Cables". The field suggests categories you've used before so they stay consistent, but you can type a new one.
Quantity / UnitHow many, and the unit ("each", "box"). Quantity must be a whole number (0 or more).
Unit costOptional per-unit price. Used to value parts logged on tickets and to total repair spend in reports.
LocationWhere it's stored, e.g. "Tech closet".
💡
When you log a part on a help-desk ticket from your inventory, its on-hand count drops automatically (and is restored if you remove the part). See Attaching a device & logging parts.

Editing items & the history view #

Inventory rows are fully editable, and every change to an item's count is recorded.

  • Edit: click Edit on a row to change any field (name, category, location, cost, quantity). Quick adjust is still there for a fast count change.
  • History: click History on a row to see a timeline of that item, with manual quantity adjustments and parts consumed against tickets, newest first.
📅

Recurring tasks

Never forget the quarterly switch-room cleaning again.

Setting up recurring tasks #

Capture the routine maintenance your team should do on a cadence. Overdue and due-this-week tasks surface on the dashboard. Add them under Recurring Tasks → + New task.

FieldNotes
Task titleRequired, e.g. "Clean switch-room fans".
DescriptionOptional checklist or notes.
FrequencyDaily, Weekly, Monthly, Quarterly, or Annually.
Next dueDefaults to one interval from today, but you can set any date. Change the frequency on an existing task and the next-due date recalculates.
ReminderOptionally email a reminder a chosen number of days (0–90) before the due date, to the assignee (or the tech director if unassigned).

Marking done, history & filters #

As tasks come due, mark them done and keep a record of who did what.

  • Mark done advances the task to its next occurrence and records the completion (who and when).
  • The Active / Completed toggle switches between upcoming tasks and the history of past completions.
  • The assignee filter narrows the active list to one person's tasks.
✦

Budget forecast

Walk into budget season with a defensible replacement plan.

How the forecast works #

The Budget Forecast computes a five-year replacement plan directly from your fleet data: every device is scheduled into the school year its AUE/EOL date falls in (or purchase date plus your lifecycle policy when no AUE is set), and priced from its recorded cost, your per-model overrides, or your district's defaults — with inflation compounded per year.

The math is deterministic — the same data always produces the same numbers, and every figure traces back to real devices. The view shows your past-due backlog ("due now"), per-year replacement costs with growth, loss, repair, and software lines, plus a level-loaded alternative that smooths spending into even annual amounts.

Try what-if scenarios

Drag the lifecycle, inflation, device cost, and enrollment knobs — the whole plan recalculates instantly. Scenario changes are free and unlimited.

Generate the AI analysis

One click asks Claude to write the narrative around your numbers — executive summary, key risks, recommendations, and board talking points. The AI only explains figures the engine computed; it never invents its own.

Save and export

Saved forecasts keep a full snapshot of the model, so you can compare plans over time or rerun last year's report. Export any forecast as CSV or a print-ready PDF.

ℹ️
Accuracy depends on your data: purchase dates, AUE/EOL dates, and device costs drive everything. Devices the engine can't schedule are listed as data gaps rather than guessed at — the report tells you exactly what to fill in.
📊

Reports & activity

See the numbers and keep an audit trail.

Reports #

The Reports area summarizes ticket volume and resolution time, device lifecycle counts, and loaner activity, with a 14-day ticket trend. Use ↓ Export CSV to pull the figures into a spreadsheet for board packets.

Reports also includes a Parts used & repair spend table: pick a date range (it defaults to the current budget year, July 1 to June 30) to see how many of each part you consumed, across how many tickets, and what it cost. It has its own CSV export and answers questions like "how many Chromebook screens did we replace this year?"

A Tickets by help desk table breaks down open, resolved, and total ticket counts for each active help desk, so you can see where the volume is going.

The Report builder tab goes further: pick a data source, then drag fields into the columns tray — drag to reorder them (the tray order is the report's column order), click ✕ to remove, and add filters or a group-by summary. Run it, chart it, export CSV or PDF, save it for reuse, or schedule it to email itself.

One-click board report #

Click 🏛 Board report on the Reports page to open a print-ready summary built for a school-board packet: fleet size and value, devices by school and lifecycle stage, this year's purchases and repair spend, upcoming end-of-life counts, and helpdesk highlights — all in plain language with the math done for you.

It opens in a new tab styled for paper. Hit Print (or save as PDF from the print dialog) and drop it into the agenda — no screenshots, no spreadsheet surgery. School-scoped staff get a building-level version automatically.

ℹ️
Dollar figures use each device's recorded cost where present, your median per-model cost where not, and sensible per-type defaults as a last resort — the report stays honest when data is thin and improves as you fill costs in.

Activity log #

The Activity Log records who did what and when — created, updated, and deleted records across the app — so you have an audit trail. It exports to CSV.

🏫

District settings

Branding, terminology, and the numbers behind your forecast.

Branding & identity #

Under Settings → District, set how your organization appears throughout the app.

FieldNotes
District / organization nameShown in the sidebar and browser tab.
Department taglineOptional. A line under the name, e.g. "Technology Services".
Sidebar abbreviationUp to 3 letters, shown when no logo is set.
Organization logoOptional. PNG, JPG, SVG, or WebP up to 200 KB.
Organizational unit labelWhat you call your sub-units — School, Building, Campus, Site, Department, Location, or a custom word. Used everywhere those units appear.

Replacement cost & lifecycle defaults #

These settings feed the AI forecast. Good defaults make for a trustworthy budget projection.

SettingWhat it controls
Student device costDefault unit price for student devices (Chromebooks, tablets).
Staff / teacher device costDefault unit price for staff devices (laptops, workstations).
Model-specific overridesExact prices for named models — these win over the category defaults.
Device aging thresholdAge in years at which a device is considered "aging".
Device lifecycle targetExpected service life before planned replacement.
Annual loss ratePercentage of the fleet lost, stolen, or destroyed each year (default 4%).
Annual repair ratePercentage needing repair each year (default 12%).
👤

Account & security

Your password, two-factor authentication, and appearance.

Changing your password #

Go to Settings → Account → Password → Change. Enter your current password, then a new one of at least 12 characters.

If you've forgotten your password, use the Forgot password? link on the sign-in screen — you'll get a one-hour reset link by email. Administrators can also send you a reset link from the Team panel.

Setting up two-factor authentication #

Two-factor (2FA) adds a one-time code at sign-in, so a stolen password isn't enough to get in. We strongly recommend it for every administrator. Turn it on at Settings → Account → Security.

Start setup

Click Enable. Edventory shows a QR code and a manual setup key.

Scan with an authenticator app

Use Google Authenticator, Authy, 1Password, Microsoft Authenticator, or any TOTP app. Scan the QR code, or type the setup key if you can't scan.

Confirm the code

Enter the 6-digit code your app shows to verify the link.

Save your backup codes

You'll get 10 one-time backup codes. Store them somewhere safe (a password manager) — they're your way in if you lose your phone.

⚠️
Backup codes are shown only once. If you lose both your authenticator and your codes, an administrator can clear your 2FA from the Team panel so you can set it up again.

Worried a session is open on a machine you no longer control? Settings → Account → Security → Sign out everywhere ends every session except the one you're using. Changing or resetting your password does the same automatically.

Choosing a theme #

Pick a color theme under Settings → Account → Appearance. Every theme meets WCAG AA contrast.

Options range from light (Cloud, Slate, Chalk, Sage) to dark (Ink, Midnight). Vision is tuned for color-blind accessibility, and Contrast is a WCAG AAA high-contrast theme that reads well on projectors and whiteboards.

🧾

Billing & plans

Pay by card or purchase order — whatever your district uses.

Plans #

Plans are priced annually by district size, set by whichever is higher — your device count or your student enrollment. Every feature is included on every plan; nothing is gated behind a higher tier. See current limits and prices on the pricing page; manage your plan under Settings → Billing.

PlanPriceFor
Free$0/yrUp to 100 devices and up to 100 students — no charge, no card required. A real plan, not a trial.
School$750/yrUp to 500 devices and up to 500 students — a single school or small district.
Standard$1,500/yrUp to 2,500 devices and up to 2,500 students — a mid-size district.
District$4,500/yrUp to 10,000 devices and up to 10,000 students — a large district.
EnterpriseCustomBeyond 10,000 devices or students — contact us for a quote.

Paying by card #

Choose a plan under Settings → Billing → Change plan and check out securely by card. Card plans renew automatically each year, and your renewal date updates on its own.

Use Manage card & invoices to update your card, download invoices, or cancel. Card details are handled entirely by our payment processor — Edventory never sees or stores your card number.

Paying by purchase order #

Most districts pay by PO. Add your purchase order number and billing email under Settings → Billing → Billing contact, and we invoice annually before your renewal date.

Renewal reminders go to your billing email 60, 30, and 15 days before renewal. Leave the billing email blank to use the technology director's address.

💾

Data & backups

Your data is yours — export it any time.

District snapshots & automatic backups #

A snapshot is a complete export of your district — devices, tickets, inventory, loaners, team, and more — as a downloadable JSON file. Take one before a big change or to keep an off-site copy. Find them under Settings → Data & Backups.

  • Take snapshot — generate one on demand and download it.
  • Automatic nightly backups — Edventory snapshots your district every night and keeps the 14 most recent automatically.
  • Manual snapshots are kept until you delete them.
🔐

Single sign-on (SSO)

Sign in with the account your district already uses.

Signing in with SSO #

If your district has single sign-on enabled, the sign-in screen shows a "Sign in with…" button for your provider — Google or GitHub. Click it and authenticate the way you normally do.

ℹ️
Your email must already be linked to an Edventory account (your administrator invites you first), then SSO connects that account to your identity provider. SSO doesn't create new accounts on its own.
💡
Want SSO turned on for your district? Contact us — we'll enable your provider and walk you through it. SSO is configured by the Edventory team, so there's nothing technical for you to set up.
🛡️

Security & privacy

How we protect your district's data.

How Edventory protects your data #

  • Your data is isolated. Every record is scoped to your district. One district can never see another's data.
  • Sensitive credentials are encrypted. Connector tokens and service-account keys you provide are encrypted at rest.
  • Strong sign-in. Passwords are securely hashed, optional two-factor is available to everyone, and repeated failed sign-ins are rate-limited.
  • Least-privilege Google access. The Google integration requests only Chrome device and license scopes — never user email or files.
  • You can export any time. Snapshots let you keep your own off-site copy of everything.
📄
For data-handling specifics, see our Privacy Policy. Have a security or compliance question? Get in touch.