Catalog and People directory
Students and instructors see the courses they belong to and the people in them. Administrators manage the catalog itself, so course creation is not something an instructor improvises.
Capability
Course work that stays inside its membership boundary
A course space holds material, announcements, discussion, and files for the people enrolled in it. Membership decides what loads, not a sharing link that outlives the term.
What a course space contains
Everything a course needs sits in one place, and each part answers to the same membership list.
Permissioned file tree
Course files are a real tree with per-node permission, not a flat drop box. What a member can open is decided by their place in the course, and every download is checked at request time.
Announcements
Announcements carry rich content and paginate, so a long-running course does not become an unreadable wall. Each one can open into a nested discussion instead of splintering into email.
Discussions and polls
Course-scoped threads with comments, likes, optional polls, and protected attachments. Removal is authorised, so moderation leaves a trail rather than a silent gap.
Per-member preferences
Membership is not only a permission. Each member carries their own preferences within a course, so the same space can be read the way its participants actually work without changing what anyone else sees.
The facility newspaper
Some things are not course news. Administrators publish facility-wide items that every authenticated role application can read, kept deliberately interaction-free: it is a noticeboard, not another discussion surface.
Do it, step by step.
The manual covers this as a task, with prerequisites, what finishing looks like, and what to do when it does not work.
Bring Mirket to your facility.
Run it on your own infrastructure or let us host it for you. Both licences ship the same product; the difference is who operates the data plane.