Plans, limits and usage

Where your own numbers are

This article cannot print them, and deliberately does not try: the plans are rows a super admin can edit, so a figure written here would be out of date by the next release. Two screens hold the real ones, and they are the only ones to trust.

• Organisation → Billing names the plan you are on, lists every plan beside it with what each includes, and shows the four numbers you are measured against.
• Organisation → Usage shows what you are currently consuming against each of those numbers, broken down by workspace.

If you are on a personal account rather than a school's, both are still yours — a single-seat account can reach the page it upgrades from.

What is limited

Plans cap six things: published experiences, storage, active learners, staff members, workspaces, and scenes per experience.

• Published experiences — how many may be live at once. Drafts are never counted; unpublishing one frees a place immediately.
• Storage — the size of everything in your asset library. A binned file does not count while it waits.
• Active learners — people who have done something in the last twelve months.
• Staff members — colleagues who hold an account in your organisation. ⚠️ An invitation is checked against this one, and the entry plans include very few, so this is not a way to give a class of children accounts. See Getting a class into your experience.
• Workspaces, and scenes per experience.

What the higher plans unlock

Five things, and here is what each one actually is:

• Branching scenarios — an experience where the learner's choice decides what happens next, rather than everyone walking the same path. Good for a decision you want people to practise making. See Authoring a branching scenario.
• Custom themes — your own colours and lettering on a published experience, instead of the ones Panova ships. See Themes and branding.
• LTI 1.3 launch — the standard that lets a learning management system (Canvas, Moodle, Blackboard and others) put an experience inside a course. Learners open it from the course, and their marks go back to its gradebook. It is the only route that does both without anybody typing a register. See Connecting your LMS with LTI 1.3.
• Data access — two ways for other software to read your Panova data: an API, which a developer can call from a script or a dashboard, and an MCP server, which lets an AI assistant answer questions about your content. Neither is anything you need in order to teach. See Data access: the API and the MCP server.
• Priority support — a named person on our side.

At a limit

Reaching a limit stops the action that would exceed it and says so — it does not delete anything or silently unpublish. Drafts are never capped; only publishing is. Publishing an experience that is already live is never refused, because it is not taking a new place.

Active learners are the exception. That figure is measured and reported, and it never blocks anybody. Stopping somebody in the middle of an assessment over their institution's billing is the wrong person to punish. Going over shows on Usage and is a conversation about your plan, not an outage.

The two people meters warn you in advance; the other four do not. As your staff-member or active-learner figure approaches its ceiling, Panova tells the organisation's admins — again when it passes it, and again if somebody is actually turned away. Published experiences, storage, workspaces and scenes give you no warning: you meet them at the door, in the message that refuses what you were doing. That is why a publish can be refused on a day nothing had told you it was coming.

Changing plan

Organisation → Billing. Card-paid plans change immediately through the billing portal. Enterprise is quoted, so requesting it opens a conversation rather than charging a card.

Securing your account

Account → Security offers two-factor authentication and passkeys. If your organisation has anything worth protecting in Panova — and learner records qualify — turn one of them on.