The lesson library — Theta Docs

Your organization's Lessons tab is the single list of cases you can put into a course. It answers one question — what do we have? — and the course builder's "Add a lesson" picker reads the very same list, so the two can never disagree.

One case, one owner

A case belongs to exactly one organization. That ownership is the whole permission model:

Every instructor or admin of the owning org can open, edit, delete and use it. There is no separate "shared with me" list to reconcile, and no per-person ownership — a colleague's case is as much your org's as your own.
Whoever authored it is recorded for attribution only. It grants no extra rights, and it takes none away when they leave.
Saving a case in an organization is publishing it to that organization. There is no second "add to library" step, and no private-draft state to forget about.

Where a case gets its organization

The Designer always works inside one organization, shown at the top of the page. Cases you create there belong to it. If you're staff of more than one org, switch between them from that same header — the list, and every save, follow the switch.

Putting a case in front of students

That happens in the course, not the library — open the course, go to its Build tab, and use Add a lesson. The picker lists your organization's own cases and the Theta case bank, so everything you could reach from the library is reachable from there.

It works this way on purpose. Adding a case to a course is never just "add" — the same case can be a relaxed practice item in one course and a timed exam in another, and mode, attempt limit, availability window, time limit, prerequisite gating and position in the curriculum all live on the course. A button in the library could only ever do half of that, and would publish a half-configured item to enrolled learners in the meantime. So the library has no such button.

You can add the same case to as many courses as you like. Removing it from a course removes that one placement; the case itself stays in your library.

The Theta case bank

Theta publishes a bank of ready-made cases that every organization can draw on. These are the only cases that reach you from outside your org — there is no organization-to-organization sharing.

There are two ways to teach one, and the difference matters:

	Add it to a course	Copy
What you get	The case, by reference	Your own version, owned by your org
Can you edit it?	No	Yes, every element
Theta's later fixes	Reach your course automatically	Don't reach your copy
Where you do it	The course's Build tab	The Copy button in the case bank
Best for	Teaching the case as designed	Wanting a different case built on that base

Adding it to a course is the right choice most of the time: your learners get Theta's maintained version, and improvements arrive without you doing anything. You never need to copy a case just to teach it.

Copy puts the case into your organization. From that moment it's an ordinary case of yours — edit any element, rename it, change its clinical settings — but it has left Theta's maintenance stream. Copies are labelled with the case they came from, so you can always tell where one started.

Copying doesn't use the case up. The original stays in the bank, marked Copied so you know you've been here, and stays addable to a course by reference. You can copy the same case twice — to compare two variants, or to start over — and the second copy is named "… (copy)" so the two are easy to tell apart in your Lessons list.

Copying is not a way to "customize and still get updates" — those are mutually exclusive by design. If you only need trainees to test a Theta case under your own clinical conventions, don't copy it: add it to the course by reference and set the applied preset on the course instead. See Element presets.

Finding a case

The library is a table, because a real one gets long. Above it you can:

Search — matches the case name and the author.
Contains — narrow to cases that include a particular test (audiometry, tympanometry, otoscopy…). Usually the fastest way to find the one you mean.
Course — show only the cases in a particular course. It also offers Not in a course, which is how you spot work that never got assigned.
Columns — hide any column you don't use.

Every column header sorts, so "what did I touch last?" is one click on Updated. Filters and search apply to the whole library, not just the page you're looking at.

What a row tells you

The case name, and the Edit button, open it in the Designer.
Published — this case of yours is in the Theta case bank, so other organizations can teach or copy it. Only Theta's own staff can publish.
Copied from "…" — this case began as a copy of another.
Contains — one icon per kind of element in the case, then how many elements it holds in total.
In courses — the course it's in, or a count when it's in several. Hover the count to see the names; click to jump to any of those courses' Build tabs.
The ⋯ menu holds the rest — view submissions, publish, delete.

On a case-bank row there is one button, Copy, because copying is the only thing a library can do with a case it doesn't own.

At a glance

A case belongs to one organization; all of that org's staff manage it.
Saving a case in an org puts it in that org's library — there's no publish step.
Curriculum is built in the course's Build tab, never from the library.
The same case can be in many courses, with different settings in each.
A Theta case bank case is either added to a course (by reference, stays current) or copied (your editable version, no longer updated).
To change how a referenced case behaves, apply a standard to the course.