Skip to content
Docs
English
Esc
navigateopen⌘Jpreview
On this page

Fuxam CMS

FuxamCMS is the institution's administrative back office in OrgHub — academic structure, courses, programs, exams, reporting, and related campus operations.

FuxamCMS is the campus management module of Fuxam Web: the institution’s administrative back office. You reach it through OrgHub, the central administration workspace opened from the main dashboard navigation. Where FuxamLMS is where teaching and learning happen day to day, FuxamCMS is where registrars, academic planners, exam officers, and institution administrators define structure, enroll people, run assessments, and produce institutional data.

OrgHub brings together users (via Base), courses, study programs, curriculum, exams, statistics, and related campus operations in one place. It automatically opens to the first page your role permits. If you see a different starting page than a colleague, your roles and permissions and your institution’s feature packages determine which sections are visible.

Why it matters

Universities need a single source of truth for academic structure and administration. Without it, curricula drift from what cohorts actually study, course rosters diverge from program plans, exam rules become inconsistent, and reporting depends on spreadsheets that nobody trusts. FuxamCMS exists so that:

  • Structure comes first — modules, curricula, terms, and rooms in the Database feed planning and enrollment instead of living in disconnected files.
  • Programs and cohorts stay coherent — study programs, versions, and cohorts connect people to the curriculum they are supposed to follow.
  • Operations scale — course administration, bulk enrollment, exams, and statistics are available to the staff who need them, filtered by permission.
  • Compliance and documentation have a home — health-insurance reporting (GKV), smart documents, and time tracking sit alongside core academic ops when your institution enables them.

Getting OrgHub right early — who can see what, which features are on, and how Database relates to Planning — prevents months of confusion later.

How this fits into Fuxam

Fuxam Web is one foundation plus three modules. Base holds shared identity and collaboration. LMS is the learning surface. Apply is admissions. CMS (this section) is administration through OrgHub.

In a typical lifecycle, an applicant is reviewed in OrgHub (Apply tools under Management), becomes a user with a role in Base, is placed in a cohort and curriculum in CMS, takes courses in the LMS, and is assessed and reported on through Exam Center and Statistics Center.

How OrgHub areas relate

Inside OrgHub, work usually flows from foundational data outward:

Area Role in the institution
Database (Academic structure) Modules, curricula, rooms, and terms — the building blocks everything else references.
Management Day-to-day admin: Courses, Planning / Programs, and Applications when Apply is enabled. Users live in Base User Management.
Exam Center Create, manage, and grade exams when exam management is enabled.
Statistics Center University-wide exports and personal reports when Statistics Center is enabled.
Extended CMS Health insurance, Smart documents, and Time tracking when their feature packages and settings are on.

Key concepts

Concept Meaning
OrgHub The administration workspace. Sidebar groups and pages are filtered by permissions and enabled features. See OrgHub basics.
FuxamCMS The campus management module: academic structure, course admin, programs and planning, exams, reporting, and optional add-ons.
Sidebar groups Four collapsible groups in OrgHub: Management, Exam Center, Statistics Center, and Database. Groups with no permitted children are hidden.
Role permissions Fine-grained rights on a role (for example, read curricula). Without the required permission, a page simply does not appear.
Feature packages Contract-level capabilities (for example, FuxamCMS — Planning). Sections can be absent for the whole institution until enabled.
Institution settings Extra toggles (Exam Center, Statistics Center, Application Management, and similar) that must be on even when the package exists.
Module / curriculum / cohort Academic building blocks: what is taught, how it is structured across a program, and which group of students follows that path.
Favorites Starred OrgHub pages pinned at the top of the sidebar for quick access.

What’s in OrgHub

OrgHub’s left sidebar is organized into four collapsible groups. Each group contains pages that are filtered by your role’s permissions and by which features your institution has enabled.

Roles and responsibilities

Who Typical CMS work
Institution administrators Enable features and settings, design roles, and keep OrgHub access aligned with job functions.
Academic planners / program managers Maintain Database, study programs, cohorts, and module planning.
Course administrators Browse and configure courses, enrollments, and links to academic structure.
Exam officers / faculty with exam access Work in Exam Center; use Statistics Center where reporting permissions allow.
Student services / registrar Users and invites (Base), documents, insurance, and cohort membership as applicable.

Access is never implied by job title alone — it follows the permissions on the user’s role. Configure those in Roles and permissions.

Where to start

  1. Read OrgHub basics so the sidebar and Favorites make sense.
  2. Confirm your own visibility model in Permissions, features and visibility.
  3. If you are building the institution from scratch, start in Academic structure, then Programs and planning, then Courses management.
  4. People and roles live in User Management — set them up before expecting OrgHub pages to appear for staff.

In this section

Last updated on July 20, 2026

Was this page helpful?