Link courses to a database

Connect OrgHub courses to module versions in your academic Database for structured study progress tracking, bulk sync, and connection management.

Fuxam can connect a course to a module version in your academic Database. This link ties the course’s activity and completion data to your institution’s curriculum structure, enabling accurate study progress tracking across study program cohorts, module planning, and reporting.

Linking is an administrative bridge: the module version carries the academic identity (credits, examination requirements, versioned configuration managed under Modules); the course is the delivery space where teaching, content, and participation happen in FuxamLMS. The connection tells OrgHub that progress in this course should count toward that module in a student’s programme structure.

Why it matters

Universities separate what a student must complete (curriculum modules) from how it is taught (course offerings). Without a database link, a course can run successfully in the LMS while study plans and academic reporting have no authoritative way to attribute completion to the correct module version.

For ECTS-based institutions, that gap creates reconciliation work at the end of term — manual spreadsheets, disputed credit records, and misaligned cohort dashboards. Linking closes the loop early: when a student progresses through a linked course, OrgHub can interpret that activity against the module version that appears in their curriculum and cohort study plan.

Linking also supports operational consistency. When module metadata changes (display name, version label), Sync All Courses propagates updates across every linked offering instead of editing courses one by one.

How it fits

Course linking sits between academic structure definition and course delivery in OrgHub.

Typical sequence: define the module version → create an empty course → link course to module version → configure Course settings → build content or assign a learning journey → enroll participants → students open the course and progress feeds academic structure.

Key concepts

Understand the connection options

From a course’s detail page or from the Courses table, you have three database connection actions:

This constraint protects academic integrity: once students engage with content in a course tied to a module, changing the underlying module association could distort progress records. Plan linking before adding content blocks or importing a SCORM learning journey.

Link a course to a module version

Choose the module version that matches the intended offering — including the correct version label for the cohort or term. Linking the wrong version can misattribute credits and examination requirements even when the course title looks correct.

After linking, the Connected modules section in Course settings reflects the association. You can also start from Link module to course on the module side when that workflow fits your team better.

Sync all courses

If your module version data has been updated in the Database and you want those changes reflected across all linked courses, select Sync All Courses from the Courses table toolbar. This updates metadata (such as the module name or version label) for every linked course at once.

Run a sync after substantive module version edits — for example, renaming a module for a new catalogue year or correcting a version display label — so linked courses stay aligned without manual per-course updates. Sync updates connection metadata; it does not replace thoughtful curriculum or enrollment changes elsewhere in OrgHub.

Remove a course connection

To unlink a course from its module version, open the course’s connection settings and select Remove Course Connection. The course remains in Fuxam but is no longer tied to an academic module.

Removing the connection does not delete course content or enrollments. It stops progress in that course from feeding the unlinked module version in study progress tracking. Consider whether cohort study plans still reference the module before unlinking mid-term.

Best practices

• Link before content. Create and link an empty course, then build the learning journey or add content. Reversing order blocks linking entirely.
• Version discipline. Always select a specific module version, not an informal module nickname. Manage versions in Manage module versions.
• Sync after catalogue updates. When module metadata changes institution-wide, use Sync All Courses from the Courses table rather than editing linked courses individually.
• Coordinate with curriculum teams. The same module version should appear consistently in curricula, cohort study plans, and the linked course offering.
• One offering, one link. If you need a separate delivery space for a different module version, create a new course rather than reusing a content-heavy course.
• Configure Course Settings alongside linking. Capacity, tabs, and rating schema still belong on the course after the academic link is in place.

Common pitfalls

FAQ

Related pages