Fuxam Base
The shared foundation layer of Fuxam Web — User Management, Calendar, Chat, and the Info Hub — used across the LMS, CMS, and Apply.
Fuxam Base is the foundation every institution starts with. It contains the day-to-day tools that everyone uses — the people directory, the calendar, messaging, and announcements — regardless of which additional packages your institution has enabled. Where the LMS, CMS, and Apply each serve a specific audience and stage of the journey, Base serves all of them at once.
Because Base is shared, the concepts you learn here reappear across the whole platform: the same users, the same appointments, the same channels. Understanding Base first makes every other module easier to reason about.
Why Base exists
Every institution, whatever it teaches, needs a handful of the same primitives: a trustworthy record of who belongs to the organization, a way to reach those people quickly, a shared sense of when things happen, and a channel for official notices. Rebuilding those primitives separately inside each module would be wasteful and — worse — would fracture the data, so a student’s identity in a course would differ from their identity in admissions.
Base solves this by providing those primitives once and letting every module draw on them:
- One identity per person. A user created in User Management is the same account whether they act as an applicant, a student, or a teacher.
- One schedule. The Calendar aggregates appointments from every course and context a person can access, so nobody has to stitch together separate timetables.
- One place to talk. Chat connects colleagues and students in real time, independent of any single course.
- One authoritative noticeboard. The Info Hub delivers targeted, trackable announcements.
How Base relates to the modules
The LMS, CMS, and Apply are built on top of Base and continuously read from and write to it. The relationship is best understood as a foundation supporting the functional modules above it.
Concrete examples of the two-way flow:
- The CMS defines cohorts, study programs, and rooms; Base’s Calendar schedules appointments against those cohorts and rooms, and the Info Hub targets announcements at them.
- The LMS creates courses and enrollments; those enrollments produce course chat channels in Base and course appointments on the Base calendar.
- Apply admits people; each admission becomes a Base user with a role, ready to be reached by Chat and the Info Hub.
Key concepts
| Term | Meaning |
|---|---|
| User | A person’s account in the institution, with a role that governs access. |
| Role and permission | Named permission sets that decide what each user can do — for example, creating calendar appointments or using Chat when it is enabled for your institution. |
| Group | A reusable collection of users used for targeting messages, announcements, and appointments. |
| Cohort | A CMS-defined class of students that Base features can address as one audience. |
| Appointment | A scheduled event (lecture, meeting, deadline) shown on the Calendar. |
| Channel | A chat conversation — direct, group, or course-linked. |
| Announcement | An Info Hub post published to a chosen audience with read tracking. |
In this section
User Management
Create, edit, view, and delete users; manage groups, roles, custom columns, and invitations.
Calendar
View schedules and create, edit, and delete appointments across courses, cohorts, and rooms.
Chat
Message colleagues and students in direct conversations and channels.
Info Hub
Publish announcements, target audiences, use templates, and track who has read them.
Roles and responsibilities
Who uses what in Base depends on role and permissions, but the broad pattern is consistent:
- All users read the Calendar, receive Info Hub announcements, and use Chat (where enabled).
- Teachers and organizers create calendar appointments for their sessions and lead course channels.
- Administrators manage users, roles, and groups, and typically author official announcements.