Learning journey
Understand the learning journey as the structured path of sections and content blocks students complete in a course — how teachers build it, assign access, and monitor progress.
The Learning Journey is the structured path students follow through a course in FuxamLMS. Content is grouped into sections, with optional standalone blocks outside any section. Each step is a content block — a file, video, quiz, assignment, Workbench document, or other activity.
Teachers and course editors with permission to edit the learning journey build the journey inside the course. Students open the same Learning Journey tab to work through content, track progress, and complete blocks. In university terms, the journey is the course syllabus made interactive: it sequences materials, encodes prerequisites, and feeds grading and analytics.
Why it matters
Without a learning journey, course materials tend to scatter across Drive folders, chat threads, and email attachments. Students struggle to answer “what do I do next?”, and staff lack a single place to manage order, due dates, and completion.
A well-designed journey:
- Gives every enrolled student the same ordered path through the module
- Lets teachers encode pedagogical dependencies (complete reading before the quiz)
- Connects content completion to grading and analytics
- Supports reuse across terms via the Content Database
How this fits into Fuxam
The learning journey sits at the center of day-to-day teaching in FuxamLMS. Enrollment (from cohorts, booking, bundles, or manual add) grants access; teachers structure sections and blocks; students progress; analytics and grades close the loop.
| Area | Relationship |
|---|---|
| Content and assignments | Block types (Files, Video, Hand-in, Test, Workbench, and others) live inside the journey |
| Content Database | Shared journey templates and reusable blocks that sync into courses |
| Grading and analytics | Completion, grades, and engagement metrics for journey steps |
| Study programs and cohorts | Cohort and curriculum enrollment often grants course (and journey) access |
| User groups | Groups support bulk enrollment paths into courses |
| Build the learning journey (teachers) | Course-tab companion for the teacher editing interface |
| Follow the learning journey (students) | Course-tab companion for the student progress view |
Key concepts
| Term | Meaning |
|---|---|
| Section | A named group of related blocks (for example a week, topic, or unit) |
| Standalone block | A content block that sits outside any section |
| Content block | A single learning step — file, video, quiz, hand-in, Workbench, or other type |
| Publish status | Controls whether students can see a block (Published, Coming Soon, Draft, Disabled) |
| Condition / dependency | A rule that locks a block until earlier work is completed |
| Start date / due date | When a block becomes available, and when it should be finished |
| Fuxam Learning Journey | Journey source where content is built in the Fuxam editor |
| SCORM Learning Journey | Journey source driven by an uploaded SCORM package (Fuxam editor locked) |
| Learning journey database | Master journey in the Content Database; linked courses may be read-only until synced |
Teacher view vs student view
| Role | What you see |
|---|---|
| Teacher / editor | The full editing interface with Table View, Student View, and Path View. You can add sections, create or reorder blocks, set dates and conditions, and preview the student experience. |
| Student | A read-only progress view: block list, completion status, due dates, and locked steps that depend on earlier blocks. |
Use Table View for structure and dates, Path View for dependencies, and Student View before you announce new content. Full create and edit steps are in this section; the in-course overview is Build the learning journey (teachers).
Use Start learning or Continue learning, track progress, and open published blocks. Student-focused walkthrough: Follow the learning journey (students). Teachers preview the same experience via View as a student.
Roles and access
| Role | Access level | Typical responsibilities |
|---|---|---|
| Course teacher / editor | write:learning-journey (scoped to course) |
Build sections and blocks, set dates and conditions, publish content, preview as student, review submissions |
| Course administrator | read:layer + journey management rights |
Enable the Learning Journey feature, set journey source, manage enrollments and capacity, access Settings tab |
| Course Management staff | read:course-management (org-wide) |
Open and view any learning journey across the institution without direct course enrollment; cannot edit blocks |
| Institution admin | Full access | Ensure Learning Journey (and related capabilities such as the Content Database) are available for your institution; manage shared journey templates |
| Student | Enrolled in course | Open the journey, complete published blocks, submit graded work on time |
Where to start
A practical order for a new course offering:
- Confirm the course exists and the Learning Journey feature is on — Configure course features.
- Create a learning journey — sections, then blocks.
- Edit order, dates, conditions, and publish status.
- Assign access via enrollment (automatic or manual).
- Preview as a student, then monitor progress once teaching starts.
In this section
Create a learning journey
Add sections and content blocks when building a course from scratch.
Edit a learning journey
Reorder steps, update block content, and change publish status.
Assign to users
How enrollment gives students access and when to add users manually.
Monitor progress
Track per-step and course-wide completion for enrolled users.
View as a student
Preview the student learning journey, progress bar, and locked or unlocked steps.
Related pages
Build the learning journey
Teacher view inside the course shell — Table, Student, and Path views.
Follow the learning journey
Student walkthrough of Start learning, progress, and locked steps.
Content and assignments
Block types, hand-ins, Workbench, and Drive.
Content Database
Reuse and sync shared journeys and blocks across courses.