Course settings

Configure course visibility, capacity, grading, features, learning journey source, and connected modules — and how they combine with institution settings and permissions.

Each course has a Course Settings page where administrators control how the course appears, who can join, which tabs participants see, and how grades are calculated. Open it from inside any course you manage in OrgHub — 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 OrgHub 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.

How it fits

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

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

Who can change Course Settings

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

Open Course Settings

You need permission to view course settings to open the page, and permission to update course settings to save changes.

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

Course features and page visibility

The Course Features section lists toggles for each course tab:

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.

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.

When a new course is created, Learning Journey, Chat, Drive, and Calendar are typically enabled by default — verify they match how the module will actually run before enrollment opens.

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

Learning journey source

When the learning journey feature is enabled, the Learning Journey Source section lets you choose:

• Fuxam Learning Journey — build content inside Fuxam.
• SCORM Learning Journey — content comes from an uploaded SCORM package.

After a SCORM package is uploaded, the source locks to SCORM until the package is removed.

SCORM (Sharable Content Object Reference Model) is a common packaging standard for e-learning content authored in external tools. Locking the source after upload prevents mixed-mode journeys that could confuse progress tracking. To return to native Fuxam content, remove the SCORM package first, then select Fuxam Learning Journey.

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 → OrgHub → 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:

• Chat settings — read-only mode and file attachment rules for the course chat lobby.
• 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.

Chat settings matter when Course Chat is enabled — 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 banner; 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 Learning Journey, Calendar, 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 journey source once. Switching between Fuxam and SCORM mid-provision is constrained by SCORM lock-in; 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 → OrgHub → Exam Center → Rating Schemas when formal grades must match exam policy.

Common pitfalls

FAQ

Related pages