Platform

Overview

Six ideas carry the whole platform: organizations, people, courses, modules, questions, and attempts. Once these are clear, every screen in the app reads as an obvious combination of them.

Organizations (tenants)

An organization is one customer’s completely separate space — its own people, its own courses, its own reporting. It has a slug (orbit-tvet-college), which becomes its subdomain, and a plan that decides what content it gets and how many courses it may author itself.

Nothing crosses between organizations. A member of one never sees another’s people or content. The single exception is platform courses, which Intermediate Data Systems authors centrally and makes available to every organization whose plan includes them — see Plans & Course Caps.

Courses

A course is the thing a member joins. It has a title, a description, a price (or is free), a pass threshold, and an optional retry limit. It belongs to one instructor, who may add other instructors as collaborators with equal access.

A course is either a draft (invisible to members) or published. Publishing is what makes it real, and you choose whether it goes to everyone in the organization or only to specific people — see Publishing.

Modules

A course is made of modules, in order. Each module is one named, independently saved unit holding the actual learning content — a video, a single image, or a set of images shown as a slideshow — plus an optional description, an optional thumbnail, optional downloadable resources, and its own bank of questions.

Modules gate each other

A member can only open module 2 once module 1 is complete: its content actually viewed and all of its questions answered. This is why the module list in the player shows padlocks. See Taking a Course.

Questions

Questions belong to a module, not to a course, so each module checks its own material. There are two types:

Type	How it's answered	How it's marked
Multiple choice	The member picks one option from three or four.	Automatically, against the option you flagged as correct.
Free text	The member writes an answer in their own words.	By hand, by an instructor or admin, on the Grading tab.

Free-text questions have real consequences for timing: nobody can see their results or certificate until every written answer on their attempt has been reviewed. See Grading.

Attempts

An attempt is one run at a whole course — not per module. It starts automatically the first time a member opens the course, records which modules they’ve viewed and every answer they give, and finishes when they press Finish Course on the last module.

What happens on completion

The attempt is scored against the course’s pass threshold. A pass produces a downloadable certificate; either way a results PDF is available. If the course sets a retry limit, that caps how many attempts a member gets; leave it blank for unlimited. See Results & Certificates.

Progress survives everything

Watched modules and saved answers are stored on the server against the attempt, not in the browser. Closing the tab, reloading, or switching to a different device all pick up exactly where the member left off.

How it all fits together

Reading it as one sentence: an organization has people; instructors build courses from ordered modules, each with its own questions; publishing a course lets members join it; and each member’s run through it is an attempt that produces a score and, on a pass, a certificate.