Licence & billing
Settings, Licence & billing (/admin/billing), gated by the billing.manage
permission.
Shows your licence, what it covers and what you use, and lets you activate, replace or remove a licence key.
The licence
Section titled “The licence”There is one Plugboard licence, priced per licensed student a year. It covers every staff account, every device and every module, campus operations included, and on managed hosting a monthly allowance of hosted AI calls. See plans. Your prices are in your order and on this page.
What the page shows
Section titled “What the page shows”One panel of facts, headed Plugboard with the licence’s state: Active, Trial, Payment overdue, Cancelled or Expired.
| Row | What it says |
|---|---|
| Licensed to | The school the licence names |
| Renews | The renewal date, or Ended once the licence has expired |
| Per licensed student, a year and Licence, a year | The prices in your order, with the currency named, for example A$ |
| Licensed students | The count the licence covers, then where it came from and how many students are active in your student system, for example “August 2026 census · active in your SIS 1,203” |
| Technical seats | How many staff accounts hold a Technical seat. A count, never an allowance |
| Business seats | Shown when any account holds one. A count |
| In use | Managed devices and connectors, as counts |
| Hosted AI this month | On managed hosting, the AI calls people asked for against the calls included, with how many are left and when the count starts again |
| Your own AI this month | When there were any: calls on your own AI account or model, which your AI provider bills, not Plugboard |
| Included | Every base module, or the modules the licence names, with a link to Modules |
| Add-ons | The campus operations modules, when the licence carries them |
Remove licence sits at the foot of the panel. Below it, Activate a licence (or Replace licence key once one is active) takes a key, and Deployment diagnostics is folded behind Show.
Licensed students and the student system
Section titled “Licensed students and the student system”The licensed count is your August census headcount, fixed for the licence year. The count of students active in your student system sits beside it as information: it is never billed on. When the two differ, the line adds that the licence is counted again from the August census at renewal. Students arriving and leaving through the year change nothing until then.
Hosted AI
Section titled “Hosted AI”Background AI calls are included and never count towards the allowance. Going over the allowance never stops AI. The page says by how many calls you are over, and shows an overage amount only when the licence prices overage: whole blocks of 1,000 calls at the licence’s price per block. A licence with no hosted allowance shows Hosted AI as Unmetered. See AI settings for the daily limit on background AI.
Seat types
Section titled “Seat types”Every active staff account is one of three seat types. Nobody picks a seat by hand: it follows from the permissions the account’s roles grant, so it cannot be under-declared. The Users page shows each account’s seat, and the role step says when a role you are granting would raise it, for example “This makes Sam a Technical seat.” It never stops the grant. On a licence priced per student, seats are counted and never priced.
An account is Technical if any of its permissions is a Technical one,
otherwise Business if any is a Business one, otherwise a free
Participant. A role holding * makes a Technical seat.
Technical covers service delivery, devices, identity, connections and administration:
| Area | Permissions |
|---|---|
| Service desk | ticket.update, ticket.close, ticket.transfer, ticket.internal, repair.update, repair.close, loan.issue, loan.return, loan.manage |
| Devices and remote | device.manage, device.laps.read, device.wipe.request, remote.start, remote.manage |
| Identity | identity.account.enable, identity.account.manage, identity.license.manage, identity.mailbox.delegate, identity.mailbox.fullaccess, identity.mfa.reset, identity.password.reset, identity.session.revoke, identity.tap.issue, directory.manage |
| Connections and monitoring | connector.manage, integration.manage, network.manage, network.diagnose, network.discovery.manage, monitor.manage |
| Desk setup | induction.manage, client.manage, workflow.manage, departments.manage, visitor.configure, label.design, flow.build, flow.publish, action.manage, flow.unattended |
| Administration | role.manage, user.manage, site.manage, feature.manage, branding.manage, backup.manage |
| Handing over credentials | secret.share.create, secret.share.manage |
Business covers money, purchasing, reporting, content, projects, changes and services, with no device, identity or technical control:
| Area | Permissions |
|---|---|
| Money | charge.raise, charge.approve, cost.manage, cost.export, billing.manage |
| Purchasing and contracts | stock.manage, software.manage |
| Projects, changes and services | operations.manage, change.manage, service.manage |
| Reporting | report.manage, dashboard.manage, dashboard.link.manage |
| Content | docs.edit, docs.manage, kb.manage |
| Approvals | approvals.manage |
Participant is free, and covers everything else:
| Area | Permissions |
|---|---|
| Viewing | Every *.view permission, and docs.viewRestricted |
| Raising and commenting | ticket.create, ticket.comment, repair.create |
| Deciding approvals | approvals.decide, operations.approve, change.approve, device.wipe.approve |
| Other | assistant.agentforce.use, ticket.ingest, audit.view, label.print |
| Front office | visitor.view, visitor.manage |
So a head of department who reads reports and approves requests is a Participant, a business manager who approves charges is a Business seat, and anyone who updates tickets or manages devices is a Technical seat. Students, parents and other requesters never hold staff seats.
See roles and permissions and the permissions reference.
Earlier licences
Section titled “Earlier licences”A licence issued before per-student pricing keeps its signed terms. An earlier licence on the one plan includes every base module, 2 Technical seats, 2,000 managed devices and, on managed hosting, 5,000 hosted AI calls a month, and can add Technical seats, Business seats, 1,000-device blocks and the campus operations add-on (Facilities, Administration, Other departments and School operations). On such a licence the page also shows:
- Technical and Business seats used against the seats included
- managed devices against the devices included, and the device blocks included against how many your fleet needs today
- connectors set up against the connectors the licence allows
- whether campus operations is included
- the licence’s prices a month, with the currency named
The role step on the Users page then adds the count, for example “This makes Sam a Technical seat, 3 of 2 included”.
Going over an included count
Section titled “Going over an included count”This applies to earlier licences; a per-student licence has no seat or device allowance to go over. Nothing is blocked. Using more seats or devices than the licence includes shows a warning on this page, is reported with your usage, and is settled at renewal as a single line, so finance does not process a small invoice every month against a fresh purchase order. Enrolling a class set of iPads or hiring a technician never locks the desk. You can also ask for seats or device blocks to be added to the licence.
A school without a licence is on a 30-day trial, on managed hosting and self-hosted alike. The trial includes every base module and no add-ons.
The trial clock starts the first time the desk checks its entitlement, and it is never restarted. In the trial’s last week a banner at the top of every page says how many days are left.
Read-only
Section titled “Read-only”The desk becomes read-only when:
- the trial has ended and no licence has been added
- a licence has expired and its grace days have passed (14 unless your licence says otherwise)
- a licence has been cancelled
While it is read-only:
- Staff can sign in and read everything. Modules stay on and their records stay visible.
- Staff can add or renew the licence here, run, verify, bring back and restore backups, export data, end support access, and look after their own account, password, MFA and passkeys.
- Admins can still take access away: remove a user, sign someone out, force MFA to be set up again, or remove someone’s passkeys. A billing lapse should never stop you off-boarding a leaver.
- Every other change is refused with a message saying how to fix it. That includes changes through API keys, the REST actions and MCP; tools that only read keep answering.
- The student portal, kiosk, parent portal, inbound email and webhooks keep accepting requests, so nothing is lost.
- Work that reaches other systems pauses: connector and SIS sync, MDM fleet sync, vendor repair and external ticket status sync, remote wipes, automation actions, network and printer sweeps, and scheduled report emails. Backups, service levels, service monitors and recurring tickets keep running.
- A banner tells everyone, and people who can manage billing get a link here.
Adding or renewing a licence ends read-only straight away. Nothing is deleted.
An expired or cancelled licence never hides records: they stay readable.
The demo is never read-only.
Entering a key
Section titled “Entering a key”Paste the key you were issued into Licence key and press Activate. The instance verifies it locally and the licence takes effect immediately.
On a managed deployment there is usually nothing to paste. Provisioning puts the licence in the environment and the instance activates it once at first boot. It acts only when there is no active licence, so it cannot overrule an activation you made yourself.
Licence keys are signed tokens. The instance holds only the public key and verifies the signature offline, so:
- There is no call home at sign-in.
- A network outage cannot disable your service desk.
- The vendor cannot silently change what you are entitled to.
If the plan changes, the plan.changed message is sent to staff who can manage
billing. That message cannot be switched off. When the change leaves something
out, a notice across the desk names it, such as “Your plan does not include
Loans”; a change that only adds says nothing.
Removing a key
Section titled “Removing a key”You can remove a licence key from this screen. The school goes back to what is left of its 30-day trial, or, if the trial has been used, becomes read-only straight away. Add-ons such as campus operations stop at once either way. The confirm step says which applies, and asks you to type the school’s name. Paste the key back to undo it.
Tier licences
Section titled “Tier licences”Licences issued on the Core, Standard, Advanced and Enterprise tiers keep working with the modules and limits they were sold with, and this page says when a licence is on an earlier plan. Licences are issued only per student. On a tier licence, Business seats are counted and shown but never flagged as over, because those licences never included any.
What the licence carries
Section titled “What the licence carries”| Plan | The one plan, or an earlier tier |
| Licensed students | The count the price covers, and where it came from |
| Price per student | The yearly price for each licensed student, and the licence’s yearly price |
| Included devices | On earlier licences, the managed device count the price covers, in 1,000-device blocks on the one plan |
| Included seats | On earlier licences, Technical seats and Business seats |
| Add-ons | Campus operations: included per student, bought on earlier licences |
| Hosted AI calls | The monthly allowance, on managed hosting |
| AI overage price | The price per 1,000 hosted AI calls over the allowance, when the licence prices it |
| Included tenants | Usually 1; more is agreed in a quote |
| Expiry and grace | When it needs renewing, and the days allowed after |
| Deployment binding | Optionally, which install it is for |
| Telemetry endpoint | Where usage counts are reported |
Telemetry
Section titled “Telemetry”Your deployment reports count-only usage every few hours.
What is sent:
- Number of Technical seats and Business seats
- Number of managed devices
- Number of students active in your student system. A count only, for the anniversary re-count, and never billed on
- Which modules are enabled
- The version and channel
- The deployment id, its region and its public hostname
- How many schools the deployment serves
- When the last backup completed: a date, never a file name or location
- A monthly count of vendor-hosted AI completions, on managed hosting. A count, never content, and only for inference we pay for. Your own key and the bundled model are not counted
What is not sent: any person’s name, any record, any ticket, any device serial, any connector credential, any content of any kind.
The endpoint normally comes from the licence itself.
Turning it off
Section titled “Turning it off”Self-hosted deployments can turn it off:
USAGE_REPORTER_DISABLED=1With it off, snapshots are still kept locally and can be downloaded with GET /billing/usage/export, which needs billing.manage. That is how a self-hosted
customer reports usage for billing without phoning home at all.
Managed deployments report as part of the service.
Authentication and replay protection
Section titled “Authentication and replay protection”The licence key is the credential used to report. We check the signature, the issuer, the audience, expiry, that the licence is not revoked, that the timestamp is within a replay window, and that the reporting deployment matches any binding on the licence.
A licence reporting from more than one install is surfaced as an alert rather than blocked, because a legitimate rebuild also produces a new install id.
Billing never deletes anything
Section titled “Billing never deletes anything”Entitlement lives in the signed licence your deployment already holds, not in the billing system. A school’s service desk keeps working through a billing outage, an expired card or a failed webhook. A licence that lapses makes the desk read-only after its grace days; it never deletes or hides your records.
A failed payment starts a conversation. Cancelling a licence remains a deliberate act.
Contracts are annual and invoiced annually by default, with automatic collection off, because most schools pay by transfer against a purchase order. A hosted payment page is available for anyone who would rather use a card or direct debit.
Version information
Section titled “Version information”Deployment diagnostics, folded behind Show, has the version you are
running, its channel and build date, and, for people with backup.manage,
whether an update is available. It also shows the licence ID, how often usage is
reported and when it was last reported. It is what support will ask for first.
Self-hosted deployments see the same in the status panel, which works when the service does not.
Self-hosting and licences
Section titled “Self-hosting and licences”A self-hosted deployment needs LICENSE_PUBLIC_KEY set in its environment so it
can verify keys. This is the vendor’s public key and is the same value for every
customer.
Key rotation is supported through a keyed map:
LICENSE_PUBLIC_KEYS='{"k_ab12cd34":"LS0tLS1CRUdJTiBQVUJM..."}'And specific licences can be refused locally:
LICENSE_REVOKED_JTIS="..."Full detail in environment variables.