Skip to content
Esc
↑↓navigate↵open⌘Jpreview
On this page

Course settings

Configure course details and capacity, course features, learning journey type and source, ratings, course chat and connected modules — and how they combine with institution settings and permissions.

Course Settings is the page inside each course where you set its details and capacity, which tabs participants see, the learning journey type, ratings, course chat rules and connected modules. Open it from inside any course you manage in Campus Management — the administrative counterpart to LMS course settings, which focuses on the teaching-and-learning experience inside the course shell.

Course settings translate institutional policy into a concrete offering: banner and description for discovery, capacity for enrollment control, feature toggles for which LMS tabs appear, grading schemas for assessments, and — when applicable — the learning journey source and connected modules that tie delivery to academic structure.

Why it matters

A course is more than a content container. Before students open it from Home, administrators must decide how it behaves: Is enrollment capped? Can participants use chat? Does progress flow from a Fuxam learning journey or an uploaded SCORM package? Which grading scale applies to content-block work?

Getting these decisions right at configuration time prevents mid-term firefighting — waitlist surprises, hidden calendar tabs, mismatched grade schemas, or academic reporting that cannot find a module version link. Course settings are the contract between Courses management in Campus Management and the day-to-day LMS course experience.

Capacity and feature choices also interact with enrollment workflows. Bulk enrollment and Manage enrollments read capacity limits when warning administrators. Course bundles grant access to linked courses whose settings still govern what participants see inside each course.

Course settings sit at the center of provisioning — after creation or editing identity fields, and before or alongside enrollment and content work.

Setting area Downstream effect
Course details and capacity Enrollment warnings, waitlists, booking behavior
Course features Which tabs appear in Open a course
Learning journey settings Fuxam-built content vs SCORM package, optionally synced from a Learning Journey DB
Ratings Grade recording for content blocks and analytics
Connected modules Academic progress via Link courses to a database

Self-service enrollment rules — who can book, default booking role, waitlists — are configured at the institution level in organization settings, not per course. Per-course capacity still applies when administrators add users and when booking is in use.

Key concepts

Term Meaning
Course details Visual identity — banner, icon, name, description, tags — and enrollment capacity.
Capacity Maximum participants. Unset means no limit. Current enrollment count displays beside the field.
Course features Toggles for the Dashboard, Learning Journey, Course Chat, Drive, and Calendar tabs. Your institution sets the defaults and can lock them.
Learning Journey Type Whether content is built in Fuxam or supplied by an uploaded SCORM package.
Learning Journey Source Optional Learning Journey DB that this course copies its journey from and stays in sync with.
Rating schema Grading scale for content-block grades in the course.
Likert scale template Qualitative rating form when user ratings are enabled institution-wide.
Connected modules Academic module versions linked for study progress tracking.

Who can change Course Settings

Action What you need
View Course Settings Permission to view course settings on the course
Save changes Permission to update course settings on the course

Access is configured in Settings → Roles & Permissions. If the page is missing, ask an administrator — see Permissions, features and visibility.

How institution and course settings combine

Decision Institution Settings This course's Course Settings
May students book themselves? Booking eligibility and default booking role —
Are waitlists used when full? Waitlist policy on / off Capacity determines when "full" applies
How many seats? — Capacity field
Which LMS tabs appear? — Course Features toggles
Which grade scale for content blocks? Institution rating schemas / user-ratings availability Rating schema (and Likert template when enabled)
Who may edit these settings? Roles and permissions Same — enforced when you open the page

Open Course Settings

Go to Campus Management → Courses and open the course.

Select Course Settings in the course sidebar.

Make your changes. An Unsaved changes bar appears at the bottom. Click Save to apply them, or Discard to undo them.

You need permission to view course settings to open the page, and permission to update course settings to save changes. Without update permission, Save is greyed out and its tooltip says You don't have permission to update course settings.

Configure settings before large bulk enrollments when capacity matters, and before linking to a module version when academic tracking is required.

Course details and enrollment capacity

The Course Details section covers identity and enrollment limits:

  • Banner, icon, name, description, and tags — how the course appears to users.
  • Capacity — maximum number of participants. Leave unset for no limit. The current enrollment count is displayed next to the capacity field.

Capacity applies when administrators add users manually and when your institution uses course booking. Self-service enrollment rules (who can book, default booking role, waitlists) are configured at the institution level in organization settings, not per course.

Identity fields overlap with Edit a course; both paths update how the offering appears in the Courses table and in student discovery flows such as Book courses.

Capacity and waitlists together

Situation What happens
Capacity set; waitlists enabled institution-wide; course full New demand can queue on the Waitlist; administrators admit from Manage enrollments
Capacity unset (unlimited) No natural "full" state from capacity alone
Capacity set to zero Warnings appear when adding users — review whether that was intentional
Waitlists off institution-wide Capacity still warns administrators; self-service waitlist controls do not appear

Course features

The Course Features section lists toggles for each course tab:

Feature What it controls
Dashboard The Course Dashboard page
Learning Journey Learning materials and student progress view
Course Chat Chat section for participants
Drive Shared file storage for the course
Calendar Course calendar and appointments

Turning off a feature hides its tab from course participants. At least one feature must remain enabled — the last active toggle cannot be switched off.

If your institution manages course features centrally (course-level overrides are turned off in the LMS settings), the toggles are read-only and the tooltip says Course features are managed by your organization. Users who can read institution settings also see an Institution defaults button that opens those defaults — see Set course defaults.

Feature choices shape the teaching workflow. Disabling Calendar removes scheduling and attendance surfaces tied to calendar and attendance in the LMS. Disabling Learning Journey hides the primary content path — consider whether learning journey assignment or content blocks still reach students through another channel before switching it off.

A new course starts with your institution's course feature defaults, or with the module's course defaults when it is created from a module version. Check that they match how the course will actually run before enrollment opens.

For a deeper walkthrough of feature toggles, see Configure course features in the LMS documentation.

Learning Journey Settings

The Learning Journey Settings section appears when the learning journey feature is enabled for your institution and the Learning Journey toggle is on for this course.

Setting What it does
Learning Journey Type Fuxam Learning Journey (content built in Fuxam) or SCORM Learning Journey (an uploaded SCORM package). Choosing SCORM shows the package upload.
Learning Journey Source Only for Fuxam Learning Journey and when the content database is enabled. Pick a Learning Journey DB to copy its journey into this course and keep both in sync. The default is No Learning Journey DB.
  • While a SCORM package is being uploaded or published, you cannot change the Learning Journey Type.
  • You can only link a Learning Journey DB while the course has no learning content. Otherwise the picker is disabled and says This course already has learning content. Remove it before linking a Learning Journey DB.
  • Switching to SCORM Learning Journey while a database is linked asks you to confirm removing the link.

SCORM (Sharable Content Object Reference Model) is a common packaging standard for e-learning content authored in external tools. While SCORM is active, the Fuxam content editor is locked — see Build the learning journey (teachers).

Native Fuxam journeys support creation, editing, and progress monitoring from the LMS. Plan the source early — especially if the course must be linked to a module version before content is added.

Grading and ratings

The Ratings section configures how grades and evaluations work in the course:

  • Likert scale template — qualitative rating form assigned to the course (when user ratings are enabled for your institution).
  • Rating schema — grading scale used for content-block grades in the course.

Changing the rating schema affects how future grades are recorded. Existing grades may reference the previous schema.

Align the rating schema with institution-wide exam types and grading scales where formal assessment policy requires consistency. Institution rating schemas are maintained under Settings → Campus Management → Exam Center → Rating Schemas. Teachers view resulting grades through View grades and course analytics in the LMS.

Additional sections

Depending on your institution's enabled features, Course Settings may also include:

  • Course Chat — Read Only (students cannot send messages) and Allow file sharing (students can share files), when course chat is enabled for your institution.
  • Storage usage — current file storage consumed by the course.
  • Connected modules — academic module versions linked to this course for study progress tracking.

Connected modules reflects database linking — the association between this delivery course and module versions in the academic structure. Link while the course is still empty; content blocks block new links.

Course chat settings matter when the Course Chat feature is on — participants access chat from the LMS communication surfaces. Storage usage helps administrators spot heavy Drive consumption before shared file limits affect teaching.

Best practices

  • Save deliberately. Watch for the Unsaved changes bar; partial edits to capacity or features do not apply until you select Save.
  • Enable features before enrollment. Students who open the course expect tabs to match the syllabus. Toggle Dashboard, Learning Journey, Calendar, Course Chat, and Drive to match how the module will actually run.
  • Set capacity when policy requires it. Pair per-course capacity with institution-level booking rules for coherent waitlist behavior on Manage enrollments.
  • Choose the journey type once. While SCORM is active the Fuxam editor is locked, and a Learning Journey DB can only be linked while the course is empty; decide before authors invest effort.
  • Link modules before content. Academic Connected modules require the empty-course linking rule — configure early in the create-and-link workflow.
  • Coordinate with bundles. Course bundles enroll users into multiple courses at once; each linked course still uses its own settings for tabs, capacity, and grading.
  • Align rating schemas with Exam Center. Prefer institution-standard scales from Settings → Campus Management → Exam Center → Rating Schemas when formal grades must match exam policy.

Common pitfalls

Pitfall Consequence Avoidance
Zero capacity left unset unintentionally Capacity warnings on every enrollment add Set a real limit or leave capacity empty for unlimited enrollment — know which you intend
Looking for waitlists only in Course Settings Cannot find waitlist policy Waitlists are institution-level; capacity is per course
Disabling all but one feature hastily Last toggle cannot be turned off; limits flexibility Plan minimum viable tabs up front
Changing rating schema late New grades use new scale; old grades may reference previous schema Set schema before summative assessment begins
Choosing SCORM then expecting Fuxam edits The Fuxam content editor is locked while SCORM is active Choose Fuxam Learning Journey for native authoring
All feature toggles greyed out Course-level overrides are off for your institution Change the Institution defaults or ask an administrator
Learning Journey Source picker disabled The course already has learning content Remove the content before linking a Learning Journey DB
Editing settings after bundle rollout Participants in bundles see changed tabs without re-enrollment Communicate feature changes to bundle programme leads

FAQ

Where do I configure waitlists and who can book?

Waitlists, booking eligibility, and default booking roles are institution-level organization settings — not per-course fields. Per-course capacity still limits how many participants the course accepts through administrator adds and booking. See Settings overview.

What is the difference between Campus Management Course Settings and LMS course settings?

This page covers the Campus Management administrator view — capacity, features, learning journey settings, ratings, course chat, and connected modules. Configure course features in the LMS documentation explains participant-facing tab behavior from inside the teaching shell. Both describe related toggles from different contexts.

Does capacity affect course bundles?

Bundle enrollment grants access to linked courses; each course's capacity and feature settings still apply to warnings and the in-course experience. Review settings on every course in a bundle before programme rollout.

Why can I view settings but not save?

You need permission to update course settings, not only to view them. Ask an administrator to review your role in Settings → Roles & Permissions.

Last updated on

Was this page helpful?