Push content to campus.

Pull content from campus.

Set golbal settings and permissions.



Independent of all other campuses (seperate DB,
Users & Content).

Independent of all other campuses (seperate DB,
Users & Content).

Mothership Project

Essentially, the Mothership Project is a high level LMS that doubles as a central course catalog. Multiple second-level LMS iterations (for each school/campus) are tied to this top level LMS (i.e., the Mothership). Then, via common cartridge imports/exports, the Mothership LMS exports course cartridges into each second-level LMS (school/campus). Additionally, content developed at each individual school/campus can be exported back up to the Mothership LMS. This capability provides clients with a central course catalog through which they can easily distribute and manage curriculum and associated Learning Outcomes across their multiple schools/campuses. Each school/campus has their own unique LMS site -- their own brand/logo etc. There would be no difference for the faculty or users at these second-level learning management system sites. The course content is simply controlled at the top level and then synced up with the second-level learning management system sites for each school/campus.

This Mothership functionality may be particularly relevant to schools, programs, or districts that may have the need to report on and manage Learning Outcomes/Objectives, provide accountability in the form of reports and curriculum management, and other administrative functions. These entities would seemingly significantly benefit from a customized solution that had a network comprised of several learning management systems, rather than just one learning management system on which all clients are served. The flexibility provided with the Mothership solution enables you to tailor each LMS to its local context.

Managing several LMS, instead of just one, could seem challenging. It should be noted that the Mothership solution is very simple to use. Course content is easily managed in one place and readily regulated across secondary LMS.

Mothership Process

Course Created in
Campus Account.

SuperAdmin selects Bundles or Courses* and pushes to campus.

If campus already has the course, the # of licenses are added to any existing licenses they have.


Client Administrator can now see the course(s). They can assign a course to any instructor by selecting a Term & Instructor.


Course shows in SuperAdmin Dashboard. Browsable by selecting a Campus > then listing courses after selecting the Term.

Nested “Bundles” can be created. Courses may be added to any bundle.

In the background, the original Cart in the Dashboard repository is unpacked and the course is created. Course setup is complete.


SuperAdmin chooses to
pull a specified course.


Cart is created in the background and imported to the Dashboard Cart Repository. Course is listed in the Dashboard by Category, with a hidden relation to the cart.

Each time a user is enrolled in a course, it subtracts from the purchased licenses.