Link module to course

Connect an OrgHub course to a specific module version so course activity and completion can feed study plans and academic reporting.

Linking connects a course to a module version in the Database. Once linked, course activity and completion data can flow into cohort study plans and academic reporting for that module version. The module remains the academic definition (credits, exams, identity); the course is the delivery space where teaching and learning happen.

Connecting always requires a specific module version — not just the module name. Create or select the correct version on the Manage module versions page first.

Why it matters

Without a link, a course can exist as a standalone delivery object while the curriculum and study plans know nothing about it. Linking closes that gap: progress in the course can be interpreted against the module that appears in the student’s program structure.

For ECTS-based institutions, that connection is essential. Credits and examination requirements live on the module version; the course is where students engage with content. The link is how OrgHub keeps those layers aligned.

How it fits

See Link courses to a database for the full course-side workflow of linking, syncing, and removing connections.

Module, curriculum, and course together

These three layers often refer to the same module version:

Worked example

Module version: Statistics for Social Sciences 2025 (6 ECTS, final exam)

1. Curriculum places 2025 in Semester 3 as a required item.
2. Module planning schedules the offering and assigns organizers.
3. Staff create an empty OrgHub course and Link Course to version 2025.
4. Students enrolled in the course can have completion interpreted against the curriculum module.

If next year you introduce Statistics 2026 with different ECTS, create a new empty course (or unlink and re-link carefully) aimed at 2026 — do not leave the old course pointing at 2025 while the new curriculum expects 2026.

Before you link

Also confirm:

• The target module version exists and has the correct ECTS, exams, and display name.
• You are linking the course that should represent this academic unit for the intended cohort or offering.
• If metadata on the module version may still change, plan a sync after updates.
• The curriculum (if already built) references the same module version you intend to link.

Link a course to a module version

Sync or remove a connection

From the Courses table you can also:

• Sync All Courses — push updated module metadata (such as display name or version label) to all linked courses.
• Remove Course Connection — unlink a course from its module version while keeping the course in Fuxam.

Best practices

• Link before adding learning content — empty courses are eligible; courses with content blocks are not.
• Prefer linking to the default version only when that version is the correct academic target; otherwise pick the version explicitly.
• After changing a version’s display name or related metadata, run Sync All Courses (or the equivalent from the courses workflow) so linked courses stay consistent.
• Keep curriculum placement and course linking on the same module version so study plans and delivery refer to one academic snapshot.
• After an ECTS change via a new version, audit linked courses so no delivery space still points at the retired snapshot for a new cohort.

Common pitfalls

• Trying to link a course that already has content blocks — create a new empty course instead.
• Linking to the wrong version (for example, last year’s ECTS) because the default was outdated.
• Removing a course connection while assuming curriculum items disappear — unlinking affects the course–module association only; curriculum structure is separate.
• Linking first and finishing ECTS/exam setup later — complete the version Details tab before students rely on the connection.

Troubleshooting

FAQ

Related pages