Handbook Web
The in-depth handbook for the Fuxam web platform — how the Base foundation, FuxamLMS, FuxamCMS, and Apply fit together and how to use them.
Welcome to the in-depth handbook for Fuxam Web, the browser-based platform your institution uses to teach, administer, and admit. This handbook is written for university staff and students who want to understand not just which button to click, but what each feature is, why it exists, how the parts relate, and how to use them well. Read it like a reference manual: start on this page to understand the shape of the platform, then dive into the module that matches your work.
Fuxam Web is organized as one shared foundation layer plus three functional modules. The foundation — Fuxam Base — provides the everyday tools everyone relies on (people, messages, schedules, announcements). The modules — FuxamLMS, FuxamCMS, and Apply — build on that foundation to cover distinct parts of the student and institutional lifecycle. Understanding this division is the fastest way to find what you need and to reason about how a change in one place shows up in another.
How the platform fits together
Think of Fuxam Web as a building. Base is the ground floor and utilities — the identities, conversations, calendars, and notices that every other floor depends on. The three modules are the floors above, each serving a different audience and stage of the journey:
- Fuxam Base — the shared foundation included with every institution: User Management, the Calendar, Chat, and the Info Hub. These features are used across the LMS, CMS, and Apply rather than belonging to any one of them.
- FuxamLMS (Learning Management) — where day-to-day learning happens: courses, content, the learning journey, attendance, grading, and course communication.
- FuxamCMS (Campus Management) — the institution’s administrative back office, reached through OrgHub: academic structure, study programs and cohorts, course administration, exams, reporting, and more.
- Apply (Admissions) — the pipeline that brings new people in, from a prospective applicant filling out a form to an enrolled student.
The modules are not silos. A person created in User Management can be an applicant in Apply, a student in the LMS, and a record in the CMS — the same identity throughout. A cohort defined in the CMS targets announcements in the Info Hub, populates course rosters in the LMS, and receives calendar appointments in Base. This is why the same vocabulary (users, roles, cohorts, courses, appointments) recurs everywhere.
The arrows read as “depends on”: each module relies on Base, and Base provides the four shared services shown beneath it.
A typical lifecycle
Following one journey end to end shows how the modules hand off to each other:
An applicant submits through Apply; an administrator reviews and admits them in OrgHub (CMS); the person becomes a user with a role; they book and attend courses in the LMS; their attendance, submissions, and grades feed CMS reporting. Throughout, Base keeps everyone reachable and on schedule.
Key concepts
These cross-cutting terms appear throughout the handbook. Learning them once pays off in every module.
| Concept | What it means in Fuxam |
|---|---|
| Institution | Your organization’s tenant in Fuxam. All users, courses, and data belong to an institution; a person can belong to more than one. |
| OrgHub | The administration workspace that hosts the CMS. Its sidebar is filtered by your permissions and enabled features. |
| User and role | A person’s account and the named set of permissions that governs what they can see and do. Managed in User Management. |
| Permissions | Fine-grained rights attached to roles — for example, permission to create and edit appointments, or to send chat messages. What you can do is governed by your role’s permissions, not your job title alone. |
| Feature packages | Optional capabilities an institution enables. Some Base features (Chat, Info Hub) and whole modules (Exam Center, Application Management) only appear when switched on. |
| Cohort | A group of students admitted and progressing together. Cohorts drive enrollment, planning, and audience targeting. |
| Curriculum and module | The academic blueprint: a curriculum organizes modules (units of study, often measured in ECTS credits) that a cohort works through. |
| Course | The teaching container in the LMS where content, appointments, attendance, and grades come together. |
Choose a module
Base — Shared foundation
The tools everyone uses: User Management, Calendar, Chat, and the Info Hub. Start here to understand the pieces every module relies on.
LMS — Learning Management
Create and manage courses, deliver content blocks, follow or build the learning journey, track attendance, publish grades, and communicate with participants.
CMS — Campus Management
Administer your institution in OrgHub — courses, academic structure, study programs and cohorts, exams, and reporting.
Apply — Admissions
Run the full admissions pipeline, from an applicant submitting a form to an enrolled student ready to start.
What each module covers
Base
Base is the layer that is always present, no matter which packages your institution has purchased. It answers the questions “who is here, how do we reach them, and what is happening when?”
- User Management — create users, assign roles, organize people into groups, and manage invitations.
- Calendar — a single, institution-wide schedule of lectures, meetings, and deadlines.
- Chat — real-time direct messages and channels for quick coordination.
- Info Hub — targeted announcements with read tracking for official notices.
LMS
The LMS is where learning happens day to day. Teachers build learning journeys, students complete content blocks, and staff manage attendance and grades. Key areas include:
- Courses — open courses, follow or build a learning journey, configure course features.
- Content — add content blocks (videos, quizzes, hand-ins, SCORM packages, and more), create Workbench documents, and review submissions.
- Calendar and attendance — manage course appointments, take attendance, and let students check in via QR code or key.
- Grading — publish grades and monitor course analytics.
- Communication — Chat, Emails, and the Info Hub in a course context.
CMS
The CMS is your institution’s campus management area, accessed through OrgHub. It complements the LMS by giving administrators control over the people and structures behind day-to-day learning. Key areas include:
- Course management — browse and manage all institution courses, enroll users in bulk, and connect courses to a learning journey database.
- Academic structure — modules, curricula, rooms, and terms (Chronology).
- Study programs and planning — manage programs and cohorts, plan modules, and assign organizers.
- Exam Center and reporting — run exams, handle assessment requests, and export institutional statistics.
Apply
The Apply module handles the full admissions pipeline — from the moment a prospective student submits an application to when they are enrolled and ready to start their studies. Applicants use a public Apply portal; administrators build application forms, configure application programs, and review applicants in OrgHub.