Overview
This setting is a Yes/No configuration option found in the institution’s Student Registration settings. Its label in the system is “Apply enrollment prerequisites to back-office usersâ€; it is internally referred to as EnablePreRequirementsOnSecretary.
In simple terms, this setting decides whether the enrollment rules that already protect students from enrolling in a Subject before they are academically ready (its “prerequisitesâ€) also apply to the school’s own registration staff when those staff members enroll or edit a student’s Subjects on their behalf.
Some Subjects in a curriculum can be configured to require that a student has already met certain academic conditions before being allowed to enroll – for example, having passed a specific earlier Subject, having accumulated a minimum number of Credits or Hours, or having achieved a minimum grade average. This setting controls whether registration staff must also respect those same conditions, or whether they remain free to enroll a student regardless.
The two possible outcomes are:
- Turned OFF (default): registration staff can enroll a student in any Subject at any time, even if the student has not met that Subject’s prerequisites. The system still shows a hint about missing prerequisites, but it never stops staff from proceeding.
- Turned ON: registration staff face the same restriction as students. A Subject whose prerequisites are not met by the student cannot be selected on the enrollment screen, and an explanatory warning appears if staff try to select it anyway.
Where It Is Used
This setting is found under: Settings > Student Registration > Subject Enrollments.
Availability: this setting only appears when Higher Education Mode is enabled for the institution (see Section 4 for the full K-12 vs. Higher Education distinction). In institutions using K-12 Mode, this setting is not shown in the settings list at all and does not apply.
Where its effect is felt: the setting changes behavior specifically on the “Curriculum Structure†screen that appears inside a student’s profile, in the Enrollments/Registrations area. This is the screen used by registration and administration staff (not the student) to manually select, for a given academic period, which Subjects, Groups (sections), and pricing categories apply to a student’s educational program.
What it does NOT affect:
- It does not change the Subject/course catalog itself, or how prerequisites are defined for a Subject (that is configured separately – see Section 3).
- It has no effect on the student’s own self-service pages, such as Online Registration or admission/application forms. On those pages, prerequisite rules are always enforced directly against the student, independent of this setting.
- It does not affect any individually granted exception a student may have for a specific prerequisite, where the institution uses such exceptions. Those work independently of this setting.
Configuration / Fields Analysis
This is a single Yes/No field – it has no nested sub-options. However, its real-world effect depends on two other things being configured first. This section explains the field itself and what must be in place for it to matter.
Field at a Glance
|
Setting label |
Apply enrollment prerequisites to back-office users |
|
Location |
Settings > Student Registration > Subject Enrollments |
|
Type of field |
Yes / No selector |
|
Default value |
No (Disabled) |
|
Applies to |
Registration / administration staff only – never the student directly |
|
Requires |
Higher Education Mode enabled |
What Each Value Means
- No / Disabled (default): prerequisite rules are informational only for staff. When staff manage a student’s Subject enrollments, Subjects with unmet prerequisites remain fully selectable. The system may still display a small warning icon next to a Subject explaining which condition(s) the student has not met, purely as a courtesy notice – this notice never blocks the action.
- Yes / Enabled: prerequisite rules become a hard restriction for staff, identical to what students already experience. Subjects with unmet prerequisites are visually marked as unavailable, and staff cannot select them – or assign a Group/section to them – for that student. Attempting to do so produces an on-screen warning explaining that the Subject cannot be enrolled because its prerequisites have not been met for this period’s enrollments, based on the student’s academic record.
Configuration Pre-requisites (what must be set up first)
For this setting to have any real effect, the following must already be true:
1. Higher Education Mode must be enabled. This is a separate, broader setting (“Enable Configuration for Higher Educationâ€) that switches the institution from K-12 Mode to Higher Education Mode. Without it, this setting is not even visible in the settings list.
2. At least one Subject must have prerequisite conditions configured. Prerequisites are defined individually per Subject, in that Subject’s own properties, under a “Prerequisites†section that can include any combination of:
- A minimum number of Hours already completed
- A minimum number of Credits already earned
- A minimum number of other Subjects already passed
- One or more specific Subjects that must already be passed
- A minimum grade average (GPA) – only available if the institution also tracks GPA
If a Subject has none of these conditions defined, this setting has no visible effect on that particular Subject – whether turned on or off – because there is nothing to check.
How the Field Interacts With Other Settings
- It works together with, but independently of, the Subject-level prerequisite fields described above – this setting is simply the on/off switch that decides whether those already-defined conditions are enforced on the staff-facing screen.
- It does not interact with, or change, how prerequisites are enforced for the student’s own self-service enrollment – that enforcement always happens, independent of this setting.
- It sits in the same configuration group as other Subject Enrollment settings (for example, timetable conflict checks); it does not depend on, or change, their behavior.
Business Logic / Behavior
Business purpose. This setting exists to let an institution choose between two enforcement philosophies:
- Strict consistency: prerequisite rules should be respected everywhere, including when staff act on behalf of a student (Enabled).
- Staff discretion: front-line registration staff should be trusted to make judgment calls – for example, when an academic advisor has approved an exception, or a data-entry correction is being made – without the system getting in their way (Disabled, the default).
Evaluation logic (business rule, inferred from configuration). A Subject is treated as “prerequisites met†only when every condition configured for that Subject is satisfied at the same time – it is an all-or-nothing check. For example, if a Subject requires both a minimum GPA and a specific earlier Subject to be passed, a student who meets only one of the two conditions is still considered ineligible for that Subject.
The informational hint is always shown (business rule, inferred). Regardless of whether this setting is Enabled or Disabled, staff can always see a small warning indicator next to a Subject listing exactly which prerequisite condition(s) are not met for that student (for example, required Hours not completed, minimum grade average not achieved, or a required Subject not yet passed). Only the ability to proceed despite the warning changes based on this setting.
Scope of the restriction (business rule, inferred). When enabled, the restriction applies Subject by Subject across the student’s whole curriculum structure on that screen. Every Subject the staff member views for that student is checked individually; Subjects that do not require any prerequisite remain freely selectable even when the setting is on.
K-12 Mode vs. Higher Education Mode
This is one of the settings that is specific to institutions operating in Higher Education Mode.
- Higher Education Mode (when “Enable Configuration for Higher Education†is turned on): this setting is available. It is meaningful because Higher Education Mode is where structured curricula, Credits, GPA tracking, and Subject-to-Subject prerequisites are normally used – for example, a college or university requiring “Statistics I†to be passed before a student can take “Statistics IIâ€. Institutions in this mode should review this setting deliberately, since it changes how registration staff behave day to day.
- K-12 Mode (when Higher Education Mode is turned off, the default for schools): this setting does not appear in the settings list at all and has no effect. K-12 institutions typically do not use Subject-to-Subject academic prerequisites in the same way, so this concept – and this setting – does not apply. There is no equivalent K-12 setting for this behavior.
Confirmed vs. assumed: it is confirmed that this field’s visibility is strictly tied to Higher Education Mode, and that its logic mirrors the student-side prerequisite enforcement onto the staff-facing enrollment screen. It is an inferred assumption (not stated anywhere in the system text) that the intended business reasoning for leaving it disabled is to preserve staff discretion for approved exceptions or corrections.
Example(s)
Example – Riverside College, Subject “Applied Statistics II†(all names below are illustrative only)
Setup used in this example:
- Institution: Riverside College, operating in Higher Education Mode.
- Subject: “Applied Statistics IIâ€, with prerequisites configured as: (a) the Subject “Applied Statistics I†must already be passed, and (b) at least 10 Credits must already be earned overall.
- Student: Jordan Ellis, enrolled in the “Business Administration†program, has NOT yet passed “Applied Statistics I†and has only earned 6 Credits so far.
Scenario A – setting Disabled (default)
The registration officer, Alex Rivera, opens Jordan Ellis’s Curriculum Structure screen to prepare next semester’s enrollments. “Applied Statistics II†appears in the list together with a small warning icon indicating the unmet prerequisites, but the Subject remains fully selectable. Alex assigns Jordan to a class Group for “Applied Statistics II†without any blocking message – for instance, because the department chair verbally approved an exception.
Scenario B – setting Enabled
With the same student and Subject, “Applied Statistics II†is now shown as unavailable on Alex’s screen. If Alex clicks on it, or tries to assign a class Group, a warning message appears explaining that the Subject cannot be enrolled because the prerequisites for this period’s enrollments have not been met, based on the student’s academic record. Alex cannot proceed unless the student meets the prerequisites, the prerequisite is removed from the Subject, or the setting is changed back to Disabled.
Note: in both scenarios, if Jordan Ellis tried to self-enroll into “Applied Statistics II†through the student’s own Online Registration page, the enrollment would be blocked in exactly the same way as Scenario B, because self-service enrollment always enforces prerequisites, independent of this setting.
Notes
- This setting only appears for institutions operating in Higher Education Mode (see Section 4). It is not present, and not applicable, for institutions in K-12 Mode.
- Changing this setting has no effect on any Subject that does not have prerequisite conditions defined. Review Section 3 to confirm which Subjects are affected before changing it.
- Enabling this setting does not remove the informational warning icon – it only turns the existing informational notice into a hard block for registration staff. Staff can still see why a Subject is flagged.
- This setting affects registration and administration staff usage only. It never changes what a student experiences when enrolling themselves; prerequisite checks for students are always active.
- Recommended use: institutions that want strict, consistent enforcement of academic prerequisites across every enrollment channel should enable this setting. Institutions that prefer to let registration staff use professional judgment on a case-by-case basis should leave it disabled (the default).