Skip to content
plugboard.appRequest a demo

Configuration

The first hour

A fresh install begins with creating the first administrator through the setup flow. Protect access to that flow until the administrator has been created.

On-premises and self-hosted. Start the application and open it. The setup flow asks for a name, an email and a password. That account gets the wildcard role, meaning every permission.

Managed. The first administrator is invited during onboarding, using the name and email you entered on the confirmation page. Check your inbox, including the spam folder, for the invitation.

If you seeded demo data, the sign-in is [email protected] with the password switchboard. Change it, or better, create your own account and deactivate that one before anything real goes in.

A fresh school requires two-factor sign-in for administrators, so the desk asks you to set up an authenticator app before anything else opens. See your account.

The first administrator of a fresh installation is guided through six steps, starting at step 1. Settings, Setup wizard (/welcome) reopens it whenever you want to review the configuration.

  1. Your desk. Which school this is: picking a NSW government school fills in your campus, timezone and NSW term dates, and setup works the same without one. Then the desk’s name; where you manage tickets (In Plugboard, In our existing ticketing system or No tickets for now); and the school’s Menu colour, Highlight and crest.
  2. Workflows. Choose the modules the team will use. Department desks and additional operational tools appear where the licence permits them. With Repairs chosen, the step asks How are student devices provided? (see below).
  3. Requests. Decide whether students and staff, and parents and guardians, need their own portals, and review the remaining identity and request-channel setup.
  4. People & access. Follow the links to administrator MFA, team roles, single sign-on and campus access. Opening a settings page does not configure it or invite anybody.
  5. Systems & backups. Configure the systems relevant to the desk and inspect the actual backup settings. Enable daily backups at 3 am is an explicit action that takes effect immediately and preserves the existing storage and retention settings.
  6. Review. Check the choices, choose Apply desk setup, then work through the launch checklist using representative accounts and requests.

Save and leave keeps your progress on the server. A reminder on Home returns you to the draft, including from another device. The desk name, colours and module choices take effect when you apply the review. Connector edits and the explicit backup action take effect separately when saved.

Describe your school instead, beside the steps, drafts the whole setup from a short description of the school, for you to review and apply. Drafting needs an AI connection; the steps work without one.

Completing setup is not a connectivity test or a backup restore drill. Test email delivery, sign-in, the chosen request paths and recovery before real work depends on them. Module choices can be changed later under Settings, Modules.

The answer decides how much of Repairs the school starts with. Lodging, loaners and each device’s repair history stay for every answer.

AnswerCover agreements and damage chargesVendor bookingRepair statuses
School-owned 1:1, including levy or fee programsOnOnThe full set
Families buy a set device through a vendor portalOffOn, once a repair supplier is connectedFour
Families bring any device that meets a specOffOffFour
Shared school devices onlyOffOffFour
Mixed or not sureOnOnThe full set

The four statuses are Open, With vendor, Ready and Closed. Vendor booking shows only while a repair-vendor connector is enabled.

The answer is applied once, when it changes. Each piece then stays its own switch under Settings, Statuses & fields. With charges off, Charge approvals leaves the menu; with cover off, Cover agreements leaves Settings. A desk that never answers keeps the options it has.

Every staff page shares the same frame: one menu in the school’s colour under the school’s name and crest, with Search or ask, New and the bell at the top, the groups of pages in the middle, and Settings and your account at the foot. On a phone it is a band across the top with the groups in a drawer.

Pages appear only if the matching module is on, so your menu is shorter than the full list until you turn things on. A missing page usually means the module is off. See finding your way around.

Settings opens Settings home, every settings page you may open in four groups. Everything under /admin belongs to Settings.

Settings, Branding. Menu colour, highlight, crest and product name. It also applies to the public self-service pages your community sees. See branding.

Settings, Modules. Each available module has a switch. Turn off what you will never use. Start conservatively; you can turn a module on later. See modules.

Settings, Statuses & fields. Repair statuses, priorities, repair types with their coverage, and the parts list with prices.

Do this before anyone lodges a real repair. Changing a status later means deciding what happens to the repairs sitting in it. See statuses and fields.

Your account, at the foot of the menu. Set up two-factor authentication for yourself before you invite anybody else, so the account with every permission is the best-protected one. See your account.

Configuration has dependencies. This order avoids doubling back:

  1. Branding, modules, statuses and fields. Above.
  2. Email. Configure SMTP or Google Workspace and send yourself a test. Everything downstream is silent until this works: tracking links, ready-for-collection notices, receipts, alerts, scheduled reports.
  3. People. A directory or SIS connector, so people exist. A repair needs somebody to belong to.
  4. Devices. An MDM connector, so a serial number resolves to a model and an owner.
  5. Roles, then users. Build the roles first. Creating twelve accounts and then discovering the role is wrong means fixing twelve accounts.
  6. Single sign-on, once there are accounts to sign in to.
  7. Everything else as you need it.

The full list with checkboxes is the setup checklist.

Most connectors have a demo mode that returns realistic fictional data instead of calling the real system. Turn it on to see a feature work before the credentials arrive, then turn it off.

Leaving demo mode on in production is the most common configuration mistake in the product. The connectors page flags it, and the compliance page counts it.

You want toGo to
Resume or review guided setupSettings, Setup wizard
Connect a systemSettings, Connectors
Turn a feature on or offSettings, Modules
Change statuses, priorities, repair types, partsSettings, Statuses & fields
Set response and resolution targetsSettings, Service level targets
Sort and route new tickets automaticallySettings, AI, and Flows
Change the product name, crest or coloursSettings, Branding
Edit the wording of an email the product sendsSettings, Notifications
Add a technicianSettings, Users
Change what a technician can doSettings, Roles
Set two-factor, password and session rulesSettings, Security
Turn on SSOSettings, Sign-in & SSO
Write help articlesSettings, Public help
Issue an API key or a webhookSettings, API & webhooks
Install a connector agentSettings, Connector agents
Schedule backupsSettings, Backups
Answer a privacy assessmentSettings, Compliance
Check the licenceSettings, Licence & billing
See who did whatLogs