π
Getting started
Create your account and find your way around.
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.
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
Serial number
e.g. 5CD1234XYZ
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.
| Field | What to enter |
| Asset tag | Your district's own identifier for the device (printed on the asset label). |
| Serial number | The manufacturer's serial. Used to match devices during sync, so keep it accurate. |
| Make / Model | Manufacturer and model name β powers the AI forecast's per-model pricing. |
| Device type | Laptop, Chromebook, iPad / Tablet, Desktop, Printer, Monitor, or Other. |
| EOL / AUE date | End-of-life, or for Chromebooks the Auto Update Expiration date. Drives lifecycle staging and budget forecasts. |
| Status | Active, In repair, Loaner, or Retired. |
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.
| Stage | Meaning |
| New | Less than a year old β recently purchased. |
| Active | Within its expected service life and healthy. |
| Aging | Approaching end-of-life (within roughly 18 months) or past your aging threshold in years. |
| EOL | Past its end-of-life or Chromebook AUE date β plan a replacement. |
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.
Scanning barcodes & QR codes #
From the Devices page, click β Scan to look up a device with your device's camera β handy on a phone or tablet while walking the building.
Open the scanner
Click Scan and allow camera access when prompted. Point the camera at the asset-tag barcode or QR label.
Or type it in
If the camera isn't available, the scanner falls back to a manual box β enter the asset tag or serial number.
Open the record
The matching device appears with its details and an Open device β link.
βΉοΈLive camera scanning uses your browser's built-in barcode reader. It works in current versions of Chrome and Edge; other browsers automatically use the manual-entry box.
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.
π
Google Workspace sync
Pull your entire Chromebook fleet from Google Admin automatically.
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.
| Field | What to enter |
| Google admin email | A Google super admin address the service account acts on behalf of. A dedicated admin account works well. |
| Service account JSON key | The .json file you downloaded in Step 2. Drag it in or paste the contents. |
| Deprovisioned OU path | Optional. 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.
What gets synced, and why these permissions? #
Edventory requests the narrowest set of scopes that make the feature work β nothing more.
| Scope | What it allows |
β¦device.chromeos.readonly | Read your Chrome device list: serial, asset ID, enrollment, organizational unit, AUE date, and last activity. |
β¦device.chromeos | Move and deprovision Chrome devices β used only when you choose to deprovision from Edventory. |
β¦apps.licensing | Read seat counts for your Google Workspace for Education and Chrome Education Upgrade licenses. |
πNone of these scopes can read user email, Drive files, calendars, or any personal content. They cover Chrome device management and license counts only. 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.
| Type | Use it when⦠|
| File | You have a CSV or spreadsheet export to upload β a one-time or occasional import. |
| Pull | Edventory should fetch from your MDM on a schedule (currently Securly). |
| API push | Another system or script should send devices to Edventory automatically. |
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.
| Field | What to enter |
| MDM provider | Currently Securly. |
| Organization URL | Your Securly organization's base URL. |
| API token | An API token generated in your MDM. Stored encrypted. |
| Client ID / Token URL opt. | Only if your MDM uses OAuth2 client credentials. |
| Sync schedule | Hourly, 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, shown in full once at creation β copy it then and store it securely.
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.
Import field reference #
These are the device fields any connector can populate. Only the match key is strictly required; everything else is optional.
| Field | Notes |
| serial_number | Manufacturer serial. Common match key. |
| asset_tag | Your district's asset identifier. |
| external_id | The source system's own device ID β useful as a stable match key. |
| make / model | Manufacturer and model name. |
| device_type / os | Type (Laptop, Chromebook, Tabletβ¦) and operating system. |
| purchased_date | Purchase date. |
| warranty_expiry / eol_date | Warranty end and end-of-life / AUE dates. |
| cost | Unit cost β feeds budget forecasts. |
| status | active, repair, retired, loaner, lost, or deprovisioned. |
| assigned_label | Free-text location or assignment (e.g. "Grade 5 cart"). |
| school_name | Matched to one of your schools/buildings. |
| notes | Any 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
Description optional
Building maintenance, HVAC, and grounds requests
Create help desk
New help desks start with a standard status board: New β In Progress β Waiting on Parts β Resolved β Closed.
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.
| Setting | Options |
| Field label | The question shown on the form, e.g. "Room number". |
| Field type | Text, Text area, Number, Dropdown, Checkbox, Date, or URL. |
| Options | For dropdowns β one choice per line. |
| Required | Whether the submitter must fill it in. |
| Sort order | Where 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.
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.
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.
| Option | How it works |
| Shared address | Edventory gives the help desk a ready-to-use address like yourdistrict-facilities@helpdesk.edventory.com. No DNS changes β works immediately. |
| Forward your own address | Keep an address staff already know (e.g. facilities@yourdistrict.org) and forward it to the unique address Edventory provides. |
| Display alias | Optional. 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.
π₯
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.
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.
| Role | Access |
| Administrator | Full access to every area, plus team management, billing, and district settings. (This is the technology-director role.) |
| Member | Access 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.
π
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.
| Field | What to enter |
| Device | The loaner's asset tag or serial. |
| Checked out to | Free text β a person, room, or cart (e.g. "Room 204", "Grade 3 cart"). |
| Due date | When it should come back. Overdue loaners surface on the dashboard. |
| Condition out | Excellent, 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.
π
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.
| Field | Notes |
| Product name | Required, e.g. "Microsoft 365 A3". |
| Vendor | Who you buy it from. |
| License type | Subscription, perpetual, concurrent, site, and so on. |
| Seats total / assigned | Powers utilization tracking β spot licenses you're over- or under-buying. |
| Annual cost | Feeds the budget forecast. |
| Renewal date | Reminders are emailed 60, 30, and 15 days ahead. |
| Auto-renews | Flag whether it renews on its own. |
π
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.
| Field | Notes |
| Name | e.g. "USB-C chargers". |
| Category | Free text grouping, e.g. "Cables". |
| Quantity / Unit | How many, and the unit ("each", "box"). |
| Location | Where it's stored, e.g. "Tech closet". |
π
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.
| Field | Notes |
| Task title | Required, e.g. "Clean switch-room fans". |
| Description | Optional checklist or notes. |
| Frequency | Daily, Weekly, Monthly, Quarterly, or Annually. |
β¦
AI forecast
Walk into budget season with a defensible replacement plan.
Running a forecast #
The AI forecast reviews your fleet β ages, AUE dates, costs, and attrition rates β and produces a multi-year replacement plan with budget figures you can take to a board meeting.
It returns an urgency index, capital budget by school year, a model-by-model replacement roadmap with justifications, a list of inactive devices worth reviewing, and a software-renewal schedule. Save forecasts to compare over time, and export them as CSV or PDF.
βΉοΈThe forecast's accuracy depends on your data. Filling in purchase dates, EOL/AUE dates, costs, and per-model prices makes the numbers far more reliable β the report flags where data is missing.
π
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.
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.
| Field | Notes |
| District / organization name | Shown in the sidebar and browser tab. |
| Department tagline | Optional. A line under the name, e.g. "Technology Services". |
| Sidebar abbreviation | Up to 3 letters, shown when no logo is set. |
| Organization logo | Optional. PNG, JPG, SVG, or WebP up to 200 KB. |
| Organizational unit label | What 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.
| Setting | What it controls |
| Student device cost | Default unit price for student devices (Chromebooks, tablets). |
| Staff / teacher device cost | Default unit price for staff devices (laptops, workstations). |
| Model-specific overrides | Exact prices for named models β these win over the category defaults. |
| Device aging threshold | Age in years at which a device is considered "aging". |
| Device lifecycle target | Expected service life before planned replacement. |
| Annual loss rate | Percentage of the fleet lost, stolen, or destroyed each year (default 4%). |
| Annual repair rate | Percentage 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.
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 fleet size. See current limits and prices on the pricing page; manage your plan under Settings β Billing.
| Plan | For |
| Free | Up to 100 devices β no charge, no card required. |
| School | A single school or small district. |
| Standard / District | Mid-size to large districts. |
| Enterprise | The largest fleets β 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, Microsoft, 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.
π
No results found
Try different words, or contact our team β we're happy to help.