Plans, permissions & modules

This help center describes everything Lurno can do. Your account shows a subset of that. If a feature you read about here isn’t in your account, it’s almost always one of three things — and this page tells you which, and what you can actually do about it.

What this does

Three independent mechanisms decide what appears in your sidebar and what the server will let you do:

Permissions — who you are inside this organization. This decides most of it.
Your subscription — the package Lurno assigned to your organization. It sets hard limits, and a small number of feature switches.
Per-organization module switches — whole product areas that are on or off for your whole organization, independent of plan and permission.

Permissions and limits are checked in the interface and on the server, so a feature you can’t see is also a feature a direct link won’t get you into.

1. Permissions — the gate that decides most things

People hold roles; roles carry permissions; permissions decide what each person can do and see. Two people in the same organization can have very different sidebars.

Lurno ships system roles — an organization administrator, an instructor, a learner, a plain member, and staff roles for mentoring, facilitating, and reviewing. Inside an organization these are marked System and are read-only: you can inspect exactly what each one grants, but you can’t change it, because it applies to every organization on the platform.

What you can do is add your own roles, if you hold permission to create custom roles. Open Org settings → Roles, choose New role, and either start blank or clone an existing role, then tune the permission grid — editing an existing custom role’s grants afterward needs permission to edit custom roles instead. Wildcard grants on a system role are never copied onto a clone — only concrete permissions come across.

Because role names differ between organizations, this help center describes the permission a task needs in plain words — “permission to update the organization”, “permission to list people”, “permission to view reports” — rather than naming a job title.

How to check yours: open your account menu at the bottom of the sidebar and choose My access. It lists every role you hold, in which organization, when it was granted, and when it expires. The same menu carries Permissions catalog for staff and learner accounts, which lists every permission the platform defines with a plain-English description of what it allows.

2. Your subscription — limits are real, feature switches are weak

Your organization is on a subscription package assigned by Lurno. There is no billing or upgrade screen in the product — no prices, invoices, or self-serve upgrade. Packages are created and assigned by Lurno staff. To change yours, talk to Lurno.

A package carries two things:

Limits, which are enforced on the server and fail closed. These cover the maximum number of members, sub-organizations, collections, lesson plans, and active enrollments. Caps count across your whole organization tree, not per sub-organization. When you hit one, the action is refused with an explicit message naming the limit and your current count against the cap — accepting one more invitation or creating another sub-organization simply won’t go through. If your organization has no subscription at all, these limited actions are refused outright.

Feature switches — Programs, Library / Collections, audience groups, Branding & Theming, Lesson Plans, custom domains, Wellbeing. Be careful with these: only Programs and Library are wired to anything in the interface, and that check passes automatically for any organization that has no subscription record. So a feature switch being “off” in a package rarely hides anything by itself.

That’s why almost every article in this help center says Plan: Any plan in its Availability box. It isn’t laziness — it reflects what the product enforces. If an article ever tells you a capability needs a specific package, it will say which, and why.

3. Per-organization module switches

Some whole areas are switched on or off for an organization as a unit. These are not plan features and not permissions — holding the right permission won’t reveal them if the module is off.

Insights (reporting) is given to an organization by Lurno. There is no screen anywhere in the product that turns it on — if your organization doesn’t have it, ask Lurno. While it’s off, the Insights and My Boards entries are hidden for everyone, and the reporting service refuses requests even from a direct link.

Wellbeing is self-serve, for someone holding permission to manage wellbeing settings. Go to Wellbeing → Wellbeing settings and turn on “Wellbeing is on for this organisation”. When the module is off, every other Wellbeing entry disappears from the sidebar — but Wellbeing settings deliberately stays, so you can always switch it back on.

AI is switched on for a whole organization by Lurno. There is no self-serve switch. While it’s off, every AI request — authoring assist, Create, the assistant, the learner tutor — is refused with a stated reason rather than an error, whatever permissions the caller holds. Sub-organizations inherit the parent’s setting.

The AI assistant carries a second organization-level switch on top of AI: a staged rollout opt-in, also controlled by Lurno. While your organization isn’t in it, the Ask button in the header and the assistant’s pages don’t exist for anyone — deliberately absent rather than disabled, because a disabled control would advertise something nobody in the organization can act on. AI being on does not imply the assistant is.

Voice needs a third thing again: a connected model provider whose account includes realtime voice. And learner voice is off by default in every organization, enabled only on request, because without a reliable age signal an unknown learner is treated as possibly a minor.

Sub-organization module access. If you run sub-organizations, open My Organizations, expand a child organization and open its Modules panel. The Module Access switches there record which modules that child should have; anything outside the parent’s package is shown struck through as “not in subscription” and can’t be switched on. Save with Save Modules.

Reading the Availability box

Most feature articles begin with a callout like this:

Availability — Plan: Any plan · Permission: requires permission to update the organization

If an article’s capability depends on a module being switched on, the Availability box says so explicitly, and names who can switch it — you, or Lurno.

Reference

Gate	Set by	Scope	Where you check it
Permissions	Your organization’s role assignments	Per person	Account menu → My access
Custom roles	Someone who can create or edit roles	Per organization	Org settings → Roles
Subscription limits	Lurno	Whole organization tree	Refused actions name the limit
Subscription feature switches	Lurno	Whole organization	Affects Programs and Library only
Insights (reporting) module	Lurno only — no in-product switch	Whole organization	Ask Lurno
AI	Lurno only — no in-product switch	Whole organization tree	Refused AI requests state the reason
AI assistant rollout	Lurno only — separate from AI	Whole organization	No Ask button anywhere means you’re not in it
Voice	A realtime-capable provider + Lurno	Whole organization	The refusal message names which one
Learner voice	Lurno, on request. Off by default	Whole organization	Learners see “Voice isn’t switched on for learners”
Wellbeing module	Someone who can manage wellbeing settings	Whole organization	Wellbeing → Wellbeing settings
Sub-org module access	Someone who can manage the parent organization	Per sub-organization	My Organizations → Module Access (not enforced)

Troubleshooting

A colleague can see a sidebar entry that I can’t. That’s a permission difference, not a plan or module difference — modules and plans apply to everyone in the organization at once. Check My access, then ask whoever manages roles to grant your role the permission the article names.

A whole section is missing, for everyone. That’s a module switch. Insights has to be enabled by Lurno; Wellbeing is enabled on Wellbeing → Wellbeing settings.

Nobody here has an Ask button, but AI works elsewhere in the product. Those are two different switches. AI enablement turns on authoring assist, Create and the tutor; the assistant is a separate rollout opt-in. Ask Lurno for the second one.

I switched a module off in Module Access and it’s still there. Those switches aren’t enforced. Use permissions to restrict what people can reach, and Wellbeing → Wellbeing settings for wellbeing specifically.

I was refused when accepting an invitation or creating a sub-organization. You hit a subscription limit. The error names which one and shows your current count against the cap. Contact Lurno to raise it.

I can see the right things in one organization but not another. Check the organization switcher at the top of the sidebar. Roles, module switches, and settings are all per-organization, so switching context changes all three at once.

I’m looking for an upgrade or billing page and can’t find one. There isn’t one. Packages are assigned by Lurno.