Curriculum & reference data

Reference data is the small set of shared lists that the rest of Lurno files things against. Subjects and grades tag your library collections and your competencies. Domains and standards live inside a curriculum. Customer types and structures describe the shape of an organization tree. You rarely edit these lists, but you pick from them constantly.

The most visible place they show up is the competency framework tree, which groups competencies by subject, grade, and — where a curriculum supplies them — domain. If you’re here because that tree has an empty level or an Ungrouped bucket, this page explains where those values come from. For the frameworks themselves, see Competencies & frameworks.

What this does

These lists are deliberately platform-managed and shared across every tenant. There is one pool of subjects, one pool of grades, and one catalogue of curriculums and structures for the whole platform — none of them carry an organization id. That’s what makes them safe to show in a picker to anyone, and it’s also why they aren’t self-serve: renaming a subject would rename it for every organization at once.

What you can control per organization is the wording, not the list. The glossary lets you replace the word Lurno shows for a concept — you type your own singular and plural for a term such as grade, so it can read as class, level, cohort, or anything else — without touching the underlying rows. See Terminology. Throughout this page, grade means whatever your organization calls that term.

Who edits what

List	Managed by	Where it shows up
Subjects	Lurno	Competency grouping, library collection filters
Grades (classes)	Lurno	Competency grouping, library collection filters, curriculum cycles
Curriculums	Lurno	Container for cycles, domains, and standards; outcome picker when building a course
Cycles	Lurno, inside a curriculum	Groups grades into bands (Elementary, Middle School, Foundation year)
Domains	Lurno, inside a curriculum	The third grouping level in a curriculum framework
Standards	Lurno, inside a curriculum	Selectable outcomes when building a course
Customer types	Lurno	Names the tiers in an organization structure
Organization structures	Lurno	The hierarchy template a tenant’s org tree follows
Competency framework contents	You	Your own frameworks, filed against the lists above

If you need a subject, grade, or domain that doesn’t exist yet, ask Lurno to add it.

Before you start

Reading requires nothing beyond being signed in.
Editing requires a Lurno platform administrator account. The pages sit behind that check, not behind an organization permission, so no combination of organization roles will unlock them.
Changes are global, and every create, update, and delete is written to the audit trail with the account that made it.
Delete buttons on these pages act immediately — there is no confirmation step and no undo. Reference rows are referenced by competencies, collections, and standards, so treat every bin icon as final.

Subjects

A subject is the broadest filing level — Mathematics, Cybersecurity, Onboarding, Product knowledge.

Open Subjects.
Choose Add Subject.
Enter a Name and an optional short Description.
Pick a Color from the eight swatches. The swatches are theme tokens rather than fixed hex values, so a subject chip stays legible in both light and dark mode.
Create. Use the pencil icon on a row to edit, or the bin icon to delete.

Subjects have no sort-order field. The list comes back alphabetical by name and the pickers that read it fall back to alphabetical too. You can click the Name column header on this page to re-sort your own view, but that is a local table preference — it does not change the order anyone else sees. If you need a specific reading order everywhere, encode it in the name.

Grades

A grade is the second filing level. Despite the name it is context-neutral: a school year, a university stage, a certification level, or a seniority band all fit here.

Open Grades (or whatever your organization calls it).
Choose Add — the button carries your organization’s term for this concept.
Enter a Name and a Sort Order — a plain number, lowest first.
Create.

Unlike subjects, grades do have a sort order, and the shared grade list is returned in that order — so the pickers that read it (the competency grade field, the library filters, the add-to-cycle dialog) follow your numbering. Leave gaps (10, 20, 30) so you can insert a level later without renumbering everything.

Curriculums, cycles, domains and standards

A curriculum is a published body of standards — a national framework, an accreditation scheme, an internal competency model. Open Curriculums to see them as cards.

Choose Add to create one, with a Name, an optional Country, and a Description.
Each card has an Active switch and an Active/Inactive badge.
Click a card to open it. It has two tabs: Cycles & Grades and Standards.

Cycles & Grades groups grades into bands within this curriculum — Elementary, Middle School, Foundation year. Use Add Cycle to create one with a name and a sort order, then use the add button on the cycle to attach grades from the shared grade pool. The dialog only offers grades that aren’t already in that cycle; the same grade can still appear in cycles belonging to other curriculums.

Standards holds the curriculum’s actual outcome statements. It splits into two sub-tabs:

Domains. A domain belongs to one curriculum and one subject — “Number and Algebra” under Mathematics. Create one with Add Domain by picking a subject, a name, and an optional description. Domains are what supply the third grouping level in a curriculum framework, which is why frameworks with no curriculum attached fall back to two levels rather than showing an empty third one.
Standards. A standard has a code, a description, a grade, a subject, and an optional domain. Grade and subject are both required. The list is filterable by grade, subject, and domain.

Standards are also the source of the platform’s shipped curriculum frameworks: each curriculum was turned into a framework, and each of its standards became a competency item carrying that standard’s subject, grade, and domain — exactly what the framework tree groups by, in that order.

What the Active switch actually does

Turning a curriculum Inactive flags it, and the per-organization curriculum list Lurno uses when configuring a tenant only shows active curriculums. It does not hide the curriculum elsewhere: the outcome picker you use when building a course lists every curriculum regardless of this switch. Treat Active as an administrative flag, not as a way to withdraw a curriculum from instructors.

Customer types and organization structures

These two describe the shape of an organization tree rather than its content.

A customer type is a tier label — District, School, Campus, Region, Department, Reseller. Create one with Add Type; it takes a name and a description. Its colour is assigned automatically from the theme palette, so there is nothing to choose and nothing to change later.

An organization structure is a named hierarchy template built from those tiers. To create one:

Open Structures and choose New Structure.
Give it a Structure Name, pick the Customer Type it applies to, and add an optional description.
Build the Hierarchy Tree. Each node is a level: pick its customer type, which supplies the level’s stored name. Once a type is picked, Add Child Type appears so you can nest a level beneath it. Add Root Level adds another top-level branch.
Create Structure. Levels are numbered L1, L2, L3 by depth.

Each node also has an Optional switch. It is saved and it renders an “Optional” badge on the structure card, but nothing in the sub-organization flow currently reads it — the level list offered when adding a sub-organization is the same whether the tier is marked optional or not. Treat it as documentation for whoever reads the structure, not as a rule.

What structures mean for sub-organizations

A structure is picked when Lurno creates a top-level organization, and inherited by every organization created beneath it. When you add a sub-organization, Lurno offers the levels sitting directly below your own level in that structure — a single level is applied automatically and shown to you, several are shown as L1/L2/L3 tiles to choose from.

A structure is not required to create sub-organizations. This is worth stating plainly, because it used to be: many tenants were set up without a structure, and for a while that made “add a sub-organization” impossible for them. That restriction has been removed. If your organization has no structure, the dialog says so, the level is left unset, and the new organization is created directly beneath yours, inheriting your customer type. Nothing about permissions or visibility depends on the level — it is descriptive taxonomy.

Sub-organizations do still count against your plan’s organization allowance, and creating one requires permission to create organizations. What a structure buys you is named tiers in the sub-org dialog and in the org tree, instead of an unlabelled hierarchy. For everything else about running an org tree, see Sub-organizations & structure.

Reference

Term	What it is
Subject	Broadest filing level; alphabetical, has a themed colour, no sort-order field
Grade	Second filing level; has a numeric sort order. Renameable per organization
Curriculum	A published body of standards; carries an active/inactive flag
Cycle	A band of grades inside one curriculum
Domain	A sub-area of one subject inside one curriculum; a framework’s third grouping level
Standard	An outcome statement with a code, filed under grade + subject + optional domain
Customer type	A tier label (School, Region, Department) used to name structure levels
Structure	A named hierarchy template of levels that an org tree follows
Structure level	One tier in a structure, numbered by depth, with an “optional” label

Troubleshooting

I can’t find Subjects, Grades, Curriculums or Structures in my navigation. They aren’t organization-admin pages. Reading the lists is open to everyone — that’s why they appear in pickers — but the management pages are restricted to Lurno platform administrators. Ask Lurno for the change you need.

My framework tree only shows two levels. The domain level comes from a curriculum, and frameworks you create inside your organization have no curriculum attached. Two levels — subject and grade — is the intended fallback, not a fault.

A competency sits in “Ungrouped”. It has no value on that grouping level. Edit the competency and pick values in the subject, grade, and domain fields; anything left at Not set stays ungrouped. A competency whose subject or grade points at a row that has since been deleted also falls into Ungrouped.

The Domain field is missing when I edit a competency. Domains only load for a framework tied to a curriculum. With no curriculum there are no domains to offer, so the field is hidden rather than shown empty.

A sub-organization lost its level after Lurno edited a structure. Saving a structure rebuilds its levels from scratch, and any organization pinned to an old level has its level cleared rather than left pointing at something stale. The organization, its people, and its permissions are untouched — only the tier label is gone.

Grades appear in the wrong order. Grades sort by their numeric sort order, not by name. Two grades sharing the same number have no defined tiebreak and may order differently between page loads — give each one a distinct value.