§ 30 · Administration

Foundation setup

Foundation setup is the bottom of the stack. Faculties, departments, programmes, campuses, academic years and terms are read by admissions, registration, timetabling, finance and graduation. Almost every unexplained empty dropdown in this manual leads back here.

What it is for

Creating and maintaining the reference data the whole system depends on.

Who can do it

Super AdminICT AdminRegistrar

Needed first
  • Decisions made outside the system: the faculty structure, the academic calendar
Where it ends

Dropdowns that are populated everywhere else.

The order matters

The Foundation Setup screen with reference data sections for faculties, departments, programmes, campuses, academic years and terms.
Foundation Setup at Setup›Foundation Setup, permission admin.foundation.manage.
Campuses→ Faculties→ Departments→ Programmes→ Academic years→ Terms→ Curriculum
CreateBecause it is needed by
CampusesEverything — scoping, timetables, fee structures, staff numbers
FacultiesDeans, programmes, graduation endorsement
DepartmentsHODs, staff profiles, courses
ProgrammesApplications, curriculum versions, fee structures
Academic years & termsRegistration windows, timetables, examinations, finance periods
Course master dataCurriculum
Do not rename codes casually

Programme codes, campus codes and course codes appear inside student numbers, staff numbers, timetable version references and document references. Renaming one does not retrospectively change the references already issued, so you end up with records that point at a code that no longer exists. If a code is wrong, fix it before the first record is created against it — and if that moment has passed, treat renaming as a project, not an edit.

The rest of Setup

The Notifications setup screen listing notification events and their channels.
Notifications at Setup›Notifications — which events notify whom, on which channel. Read alongside Communication, because a notification configured to go by email will not arrive while email sending is disabled.
The Document Repository screen holding institutional documents and policies.
Document Repository — institutional documents and policies, separate from students' academic documents.
Worked example

Opening a new academic year

1Foundation Setup → academic year 2027/2028
2Its terms, with real dates: Sep-Dec 2027, Jan-Apr 2028. Many screens default to the latest term, so creating a future term changes what colleagues see by default — warn them
3Curriculum versions for any intake starting that year
4Fee structures for the new intake, priced per year and semester
5Admission cycle, window and application fee
6Registration windows — created as Draft, opened when you are ready
7Timetable days and period grids for each campus and term — without these the Timetable Builder's dropdowns are empty
8An open financial year and period
9Check the Command Center readiness view before the first applicant arrives

Symptoms that lead back here

Reported asActually
“The programme dropdown is empty”No programmes for that campus or level
“The timetable builder has no days”No teaching days for that campus and term
“It says No configured period”No period grid for that campus and term
“Students can't register”No term, or no registration window for it
“Nobody is being billed”No fee structure matching the intake dimensions
“A Dean sees nothing”No faculty on their user record
“Every dashboard reads zero”A future term exists and screens default to it
A good habit

When someone reports an empty dropdown anywhere in the system, ask two questions before anything else: which campus and which term. That resolves most of them without opening a single screen.