Campus program
A third of your users are new every autumn.
A campus is not a company with more people in it. The population turns over on a calendar, a large part of it is not staff at all, and the faculties do not agree on anything. So the program has to survive being rebuilt every September.
Cohorts
synced, not uploaded
Faculties
own campaigns, own reports
Your LMS
delivery where students already are
Externals
outside the directory
What a campus needs
Cohorts that arrive and leave, faculties with their own rules, and a learning platform chosen years ago.
Students never appear in the staff directory and external participants appear in no directory at all. Each faculty wants its own campaigns and its own numbers. And the university already runs Moodle or Ilias, so training has to arrive there rather than in yet another portal. Last year's program should be next semester's starting point, not a rebuild.
- Cohort sync through OpenLDAP, Active Directory, API or CSV
- Onboarding and offboarding automated, so leavers drop out of campaigns without a ticket
- External participants who are not in the staff directory
- Several faculties, each with their own campaigns and their own reporting
- Delivery through the LMS the campus already runs
Tell us how many faculties and how many new students each autumn.
Twenty minutes on cohorts, directories and your LMS, and a program that is set up once and reused every semester.
Book a demoSee pricing