Edit a study program
Update a study program's name, code, program type, degree details, settings, connected curricula, and academic rulesets from the Programs table or the Settings tab.
You can edit a study program’s display name from the Programs table, or open the full Settings tab inside a program version to update details, configuration, connected curriculum, and exam policy links. Edits keep the same program identity — they do not create a new offering — so choose carefully whether a change belongs on the current version or warrants a new program version.
In day-to-day administration, light updates (rename, code correction) happen from the list view. Deeper configuration — objectives, degree metadata, program type, cohort behavior, curricula links, responsible users, tuition defaults, and academic rulesets — lives on the version Settings tab.
Why it matters
Study programs are reference points for cohorts, enrollments, planning, reporting, Apply, and exam policy. Keeping names, codes, types, and settings accurate:
- Prevents staff from opening the wrong offering in OrgHub.
- Keeps the qualification (Bachelor, Master, and similar) correctly classified for catalogs and reporting.
- Keeps connected curriculum and rules aligned with how the program is actually run.
- Avoids mixing “metadata cleanup” with “rules change for a new intake” — the latter belongs in a new version.
How it fits
| Related area | Relationship |
|---|---|
| Manage program versions | Create a new version instead of changing rules for cohorts already enrolled |
| Program versions explained | Decision guide for accreditation-driven changes |
| Manage cohort curriculum | Change the curriculum assigned to a specific cohort |
| Curricula | Manage curriculum definitions in the Database |
| Academic rulesets | Program-level exam policy; see also assignment priority |
| Study programs and cohorts | Domain model and navigation |
Before you start
- Know whether you need a display rename, a code fix, degree / type updates, or version-specific settings.
- If the change affects academic obligations for existing students, prefer a new program version and new cohorts rather than rewriting settings under an active intake.
- Confirm your role has update access (required for inline Study Program Code edits and Settings changes).
Rename from the Programs table
Use this path for a quick display-name change without opening the program.
Go to OrgHub → Management → Programs and open the Study Programs tab.
Select exactly one program row in the table.
Select Rename in the toolbar.
Enter the new Program Name and confirm.
Edit settings inside a program version
Use this path for full configuration on a specific version.
Open the study program from the Programs table.
Use the version selector in the header to choose the program version you want to edit.
Open the Settings tab.
Update fields in the available sections — for example Details (name, objective, degree metadata), Program configuration (Has Cohorts, Has Statistics, program type), Connected curricula, Responsible users, Drive folder, Default tuition fee plan, or Academic rulesets.
Save your changes.
You can also edit Study Program Code inline from the Programs table when your role has update access.
Settings reference
| Section | Typical contents | When to edit |
|---|---|---|
| Details | Name, objective, degree metadata, default study duration context | Catalog text, degree labeling, program identity |
| Program configuration | Has Cohorts, Has Statistics, program type (for example Bachelor or Master) | Structural behavior, reporting inclusion, qualification level |
| Connected curricula | Linked curriculum definitions | Defaults for how the program relates to Database curricula |
| Responsible users | Staff accountable for the program | Ownership and coordination |
| Drive folder | Associated document storage | Shared program files |
| Default tuition fee plan | Fee plan default | Financial defaults for the offering |
| Academic rulesets | Linked academic rules | Attempt limits, grading schemas, and related exam policy |
Degrees, program types, and rulesets
| Concept | What to maintain | Why |
|---|---|---|
| Program type | Classification such as Bachelor or Master | Distinguishes qualification level in configuration and reporting |
| Objective / degree metadata | Purpose and award-related details | Catalog clarity and institutional documentation |
| Academic rulesets | Policy bundle for this program (or overridden at cohort/user) | Examiners see consistent attempt and grading rules — see Academic rulesets |
When exam policy changes only for the next regulation year, combine a new program version with the matching ruleset rather than silently replacing policy under an active cohort. Assignment priority resolves user → cohort → program → defaults.
Best practices
- Rename for clarity and catalog alignment; avoid baking an intake year into the program name if versions already carry that meaning.
- Edit Settings on the version that should receive the change. Existing cohorts remain tied to the version they were created under.
- Treat Connected curricula changes as forward-looking for new users; use manage cohort curriculum when you must update study plans for an existing intake.
- Prefer a new program version when academic rules or degree structure change for the next intake.
- Keep Responsible users current so planning, admissions, and the examination office know who owns the offering.
- After renaming, align related application program labels so applicants and staff see consistent names.
Common pitfalls
| Pitfall | Why it hurts | What to do instead |
|---|---|---|
| Editing Settings on the wrong version | Cohorts on another version keep old configuration context | Confirm the version selector before saving |
| Changing Connected curricula expecting all study plans to rewrite | Existing users keep current study plan items | Update at cohort level or use cascade options when changing cohort curriculum |
| Using Settings edits instead of a new version for a major rule change | Mixes old and new intakes under one rule snapshot | Create a new version and new cohorts for the next intake |
| Renaming without updating related Apply or reporting labels | Staff and applicants see inconsistent names | Coordinate renames with admissions and reporting owners |
| Leaving program type unset | Qualification level unclear in catalogs and exports | Set type (Bachelor, Master, or your institution’s options) in Settings |
FAQ
Should I edit the current version or create a new one?
Edit the current version for metadata, ownership, and configuration that should apply to that version’s ongoing administration. Create a new program version when a new intake must follow different rules while earlier cohorts stay put.
Does renaming from the table change the Study Program Code?
No. Rename updates the Program Name. Edit Study Program Code inline from the Programs table (with update access) or via Settings as your workflow allows.
Where do I change a cohort's curriculum?
At the cohort level — see Manage cohort curriculum and Assign curriculum to cohort. Program-level Connected curricula does not by itself rewrite existing cohort study plans.
How do academic rulesets on the program interact with cohort rulesets?
A cohort assignment overrides a study program assignment; a direct user assignment overrides both. See Assignment priority.