Your plan & its limits
Your organization runs on a subscription package: the set of modules you’re entitled to, plus numeric caps on things like members and sub-organizations. This page explains what the package governs, what you can adjust yourself, and what has to go through Lurno.
This works the same whether you run corporate training, a customer academy, a university course, or a school.
What this does
Section titled “What this does”A package does two things:
- Modules. The package lists the capabilities you’ve bought — Programs, Library / Collections, audience groups, branding and theming, lesson plans, custom domains, well-being. Treat this as the commercial record of what your organization is entitled to. Only Programs and Library actually disappear from the navigation when they’re left out of a package; everything else is governed in practice by permissions, and by each module’s own settings. If you can reach something your package doesn’t cover, that’s not permission to use it.
- Limits. It sets numeric caps — maximum members, maximum organizations, maximum collections, maximum lesson plans, maximum active enrollments. Caps are the part that is genuinely enforced, by the server, at the moment you try to create something — so a cap surfaces as a refusal, not as a warning banner.
There is no plan “tier” shown anywhere in the app, no list of the modules your package includes, and no usage dashboard. You discover where you stand in two places: the Member allocations panel, which shows the member pool and how much of it is handed out, and the message you get when a cap refuses an action.
How limits are shared
Section titled “How limits are shared”Limits are counted across the whole organization tree, not per sub-organization. If a parent organization has several sub-organizations beneath it — departments, campuses, faculties, customer segments — they all draw from the same pool.
Enrolling 40 people under one sub-organization and 60 under another counts as 100 against a member limit shared by the tree. If one part of the tree is near a limit, it affects what the rest of the tree can do.
Only active people count towards the member limit. Someone you have invited but who hasn’t accepted yet doesn’t consume a place — which is why a member cap is enforced when an invitation is accepted, not when it is sent.
Distribute your member pool
Section titled “Distribute your member pool”You can slice the tree’s member pool so one sub-organization can’t consume it all.
- Open My organizations from the Settings section of your navigation.
- Find the organization whose pool you want to divide. It must have at least one sub-organization — the control is hidden otherwise.
- Choose Member allocations. On a top-level organization it sits in the row under the name, next to Add child; on a sub-organization it’s the gauge icon at the end of its row.
- The panel shows the pool as a bar: how much is allocated of the total, plus N remaining or N over budget. If the pool is uncapped it says Unlimited instead and there is nothing to divide.
- Enter a number for each direct sub-organization. Leave a field empty to leave that sub-organization Uncapped — it draws from the shared pool without a fixed cap of its own.
- Choose Save allocations — the button appears once you change a number. Allocations that add up to more than the pool are refused, both in the browser and on the server.
Only the member pool can be allocated this way. Other caps apply to the tree as a whole.
About the Module Access panel
Section titled “About the Module Access panel”On a sub-organization row in My organizations there is a settings icon that opens a Module Access panel with a switch per module. Don’t rely on it. Nothing in the product reads what it saves — the modules a sub-organization can use are decided entirely by the package on the tree, and switching a module off here doesn’t hide it, restrict it, or change anyone’s navigation.
Modules can only be changed by changing the package, which is a Lurno action. If you need one sub-organization to have a narrower set of capabilities than the rest of the tree, raise it with your Lurno contact rather than using this panel.
When you hit a limit
Section titled “When you hit a limit”Hitting a cap produces a message at the point of action rather than on a billing page. There are three variants:
- Your plan’s limit has been reached. The tree-wide cap is full.
- This sub-organization’s allocation has been reached. The tree still has room, but this sub-organization’s slice is used up — rebalance it in Member allocations.
- This organization has no active subscription. No package is assigned. Contact Lurno.
Reference
Section titled “Reference”| What’s governed | How it works |
|---|---|
| Modules | The capabilities the package entitles the whole tree to. Not adjustable per sub-organization, and not the thing that decides what most people can open — permissions do that. |
| Member limit | Maximum active members across the whole tree. The only limit that can be allocated per sub-organization. |
| Organization limit | Maximum sub-organizations in the tree. |
| Collection and lesson-plan limits | Maximum collections and lesson plans across the tree. |
| Active enrollment limit | Maximum concurrent enrollments across the tree. |
| Changing the package | Lurno staff only. No self-serve upgrade, checkout, or payment surface exists. |
Members, sub-organizations, and other terms may be renamed for your organization. See Terminology.
Troubleshooting
Section titled “Troubleshooting”I can’t find a billing or subscriptions page. There isn’t one for customer organizations. The subscriptions surface in Lurno is a platform-staff tool; it is not reachable from a customer admin account. Everything you can adjust is on My organizations.
A feature is missing or shows as unavailable. Either it isn’t in your package, or you don’t have the permission for it. The product doesn’t tell you which, and there’s no screen listing what your package includes — ask Lurno to confirm the package, and check your role first. See Plans, permissions & modules.
A module in the Module Access panel is shown as a technical key rather than a name. A couple of entries have no display name yet and fall back to their key. Since the panel has no effect anyway, you can ignore it.
I can’t create another sub-organization. The tree has reached its organization limit. Remove an unused sub-organization, or ask Lurno to raise the cap. See Sub-organizations & structure.
I can’t invite or enroll more people. The member or active-enrollment cap for the tree is full, or this sub-organization’s allocation is. Because limits are shared, check usage across the whole tree, not just the organization you’re working in. See Inviting people.
“Allocations exceed the available pool.” The numbers you entered add up to more than the tree’s member limit. Reduce them, or leave some sub-organizations uncapped, before saving.
I don’t see Member allocations. It needs an organization-admin role, and it only appears on an organization that already has at least one sub-organization — there is nothing to divide a pool between otherwise.
Member allocations says “Unlimited” and shows no bar. Your package has no member cap, so there is no pool to divide and nothing to run out of. You can still set a per-sub-organization ceiling in the fields if you want one, but nothing is being shared out.