Shell Types

CRN Shell

Automatically generated before each semester via the a process in the Enrolment Centre. These shells deliver a course to students for a specific semester.

• Creation: Enrolment Centre process

• Students: Enrolled by the Enrolment Centre

• Faculty: Teacher role is added by Departmental Support Officers in Banner, non-editing teacher added by the Hub

Development (DEV) Shell

These shells are created for testing or development purposes, often between terms. Ideal for testing changes or preparing content without affecting live courses.

• Creation: Hub

• Students: Cannot be added

• Faculty: Teacher and non-editing teacher added by the Hub

Course Template Shell

A base shell containing essential course content and resources. Provides faculty with a ready-made structure to support course preparation.

• Creation: Hub

• Students: Cannot be added

• Faculty: Teacher and non-editing teacher added by the Hub

META Shell

Used when a faculty member teaches multiple CRNs of the same course in a single semester. Centralizes content in one location, with CRN shells linking to the META shell.

• Creation: Hub

• Students: Enrolled via CRN by the Hub

• Faculty: Added via CRN by the Hub, non-editing teacher added by the Hub

More info: Click here.
Requesting a META shell: Log a ticket or email the Hub including the course code and CRNs.

Program shells

Some programs have program shells that allow faculty to share information with all of the students in a program. These are used to deliver safety training, give resources and info about placements and to schedule lab time.

• Creation: Hub

• Students: Enrolled via CRN by the Hub

• Faculty: Teacher and non-editing teacher added by the Hub

Access Levels

Teacher (Full Access)

Can edit all course content, add/modify/delete activities, and manage course settings.

Non-Editing Teacher

Can grade and view student work but cannot modify course content or activities.

Copying Content

Faculty can copy content between shells only if they are a teacher in both the source and destination shells. Click here for instructions.

Alternately the Hub can copy content from one shell to another. To request this,  log a ticket or email the Hub including the course code and CRN.

• If the requesting faculty is a teacher in both shells, the Hub can proceed with copying content

• If the faculty requests to have a Course Template Shell copied, the Hub can proceed with copying content

• If faculty requests a copy of another faculty member’s shell, approval is required from their Chair or the source shell teacher to proceed