Admin Documentation

Unit sessions: Overview

Let’s say your school is launching a new program for instructional designers.

You have carefully designed two units - Digital Learning and Learning Science - each with their own projects. You’ve written the content of the projects, you have created all supporting resources, you’ve prepared your assessments.

But at this point, the units are just templates of a learning pathway. They are the blueprints, not the actual experience.

Now, you want to run your course - that is, you want to make it available to students on given dates.

That’s where sessions come in.

Sessions take your blueprints and turn them into live entities that you can subscribe students to, and where you can follow their progress.

Before looking at how you create a session, let’s recap the differences between unit templates and unit sessions.

Templates Sessions

You design learning resources

→ Students access learning resources

You create a sequence of projects without specifying a timeframe

→ Projects are scheduled at specific dates
→ Projects can be mandatory or optional

You create project templates

→ You decide how projects are run (team composition, whether deliverables are public, how attendance is taken...)

You prepare review forms according to your assessment strategy

→ You schedule reviews

You permanently remove a project from a unit

→ You disable a project for a single session

Students can't access templates

→ Students are subscribed to sessions