Skip to content
plugboard.appRequest a demo

Start here

Setup checklist

Work through this in order. No step depends on a decision you have not made yet, and the parts that need somebody else (a service account, a DNS record, an API token) are requested early so you can carry on while you wait. The work itself is a couple of afternoons.

  • Sign in as the first administrator. A fresh install has no accounts; you create the first one. See the first hour.
  • Set the branding. Product name, logo, colours. See branding.
  • Turn off the modules you will not use. Each one you disable removes a navigation item and a set of endpoints. See modules.
  • Say how student devices are provided. The Setup wizard asks under Repairs: school-owned 1:1, families buying through a vendor portal, families bringing their own, shared devices only, or mixed. The answer decides whether cover agreements, damage charges, vendor booking and all ten repair statuses start on. See fitted to how devices are provided.
  • Set statuses and fields to match how you already work. Repair statuses, priorities, repair types with their coverage, and the parts list with prices, under Settings, Statuses & fields. Do this before anyone lodges a real repair; changing a status later means deciding what happens to the repairs sitting in it. See Statuses & fields.

Day one, in parallel: ask other people for things

Section titled “Day one, in parallel: ask other people for things”

These have lead times. Send the requests on day one.

  • An MDM API client. Jamf, Intune, Kandji, Mosyle or Chrome Enterprise. Each vendor’s steps are on its connector page.
  • An SIS API key, if you run Synergetic, Sentral or Compass.
  • SMTP credentials or a Google service account, for outbound email.
  • A certificate, if self-hosting. An internal CA is fine. See HTTPS and certificates.
  • A DNS record for the hostname staff will type. See your own domain or the managed equivalent.
  • An OIDC application in Entra or Google, if you want single sign-on. See single sign-on.

Do these in order. Each one makes the next more useful.

  • Email first. Configure SMTP or Google Workspace and send yourself a test. Everything downstream (tracking links, receipts, alerts, scheduled reports) is silent until email works.
  • Then the directory or SIS, so people exist. Without people, a repair has nobody to belong to. See Synergetic, Sentral, Compass or LDAP.
  • Then the MDM, so devices resolve. With it, a serial number typed at the kiosk turns into a model and an owner.
  • Then the rest, as you need them: warranty lookup, a ticketing system, SMS, printers, endpoint security.

Every connector has a demo mode. Turn it on to see the feature work before the real credentials arrive, then turn it off. The connectors page flags any connector left in demo mode.

  • Create roles that match your team before you create users. Roles are sets of permissions; users get roles. Building the roles first saves fixing accounts afterwards. See roles and permissions.
  • Invite your technicians. See users.
  • Turn on single sign-on if you have it, and set a fallback password on at least one administrator account, so an identity provider outage does not lock the whole team out.
  • Turn on SCIM if your identity provider supports it, so a leaver loses access the moment HR disables them. See SCIM provisioning.
  • Set up two-factor authentication on your own account. A fresh school already requires it for administrators: anyone who manages users, roles, connectors, backups or billing, erases a device or reads local admin passwords. Decide whether every staff account must use it too, under Settings, Security. See your account and sign-in security.
  • Review the email messages. Thirteen templates ship with usable wording, and most schools change two or three. Check the ones that leave the school (tracking, ready for collection, purchase receipts, parent notifications). See email messages.
  • Set up loan groups if you lend devices, and point one at an MDM smart group so the pool stays current without manual entry. Choose for each whether a returned device is lent again straight away or held until it is erased. See loan groups.
  • Set service level targets under Settings, Service level targets, if you want overdue flagging. See service levels.
  • Write three knowledge base articles. The three questions your desk answers most. Published articles appear on the public help centre. See knowledge base.
  • Open the kiosk on the machine that will run it and walk through lodging a repair as a student would. See the service desk kiosk.
  • Back up SECRETS_MASTER_KEY somewhere other than the server. A restored database without the key cannot decrypt its own connector credentials, which turns a recoverable outage into permanent loss.
  • Run a backup and verify it. Restore it somewhere and confirm you can sign in. See backups and restore.
  • Check the licence is active and the plan matches what you bought, under Settings, Licence & billing. See licence.
  • Confirm HTTPS works from a machine that is not the server, including on a phone. A missing intermediate certificate often works on a desktop browser and fails everywhere else.
  • Set up monitoring, so you hear about an outage before your users do. See keeping an eye on it.
  • Turn off any connector still in demo mode.
  • Fill in the compliance page so the answers to your school’s privacy assessment come from the system rather than from memory. See compliance answers.
  • Watch the audit log for a week. It shows who is using which parts of the desk.
  • Turn on satisfaction ratings once enough repairs are closing to make the numbers mean anything.
  • Build a flow for the triage you find yourself doing by hand, and run it in Watching mode for a week first.
  • Schedule the report your head of ICT keeps asking for.