---
title: Module groups
description: >-
  Group related modules for catalog organization and curricula planning — and
  how module groups differ from curriculum elective groups.
sidebar:
  order: 4
  hidden: true
---

A **module group** is a named collection of related modules in your institution's academic catalog — for example, "Core Modules," "Quantitative Methods," or "Language Electives Pool." Groups help staff organize the module catalog and support curricula planning by attaching modules that belong together conceptually.

Module groups sit alongside individual [modules](/docs/fuxam-web/cms/academic-structure/modules): modules remain the units of study with versioned ECTS and exams; groups are an organizational layer on top.

:::info
Module groups are **not** the same as curriculum [elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups). Elective groups control how students choose optional modules inside a curriculum. Module groups organize related modules for catalog structure and planning.
:::

## Why it matters

Large institutions maintain hundreds of modules. Without groupings, catalogs and planning views become flat lists that are hard to navigate. Module groups let program offices:

- Cluster related modules (core, methods, languages, specialization pools) under a shared name and code.
- Reuse those clusters when building or reviewing curricula.
- Give planners a clearer map of which modules belong together — before deciding which are required and which are electable in a specific program.

In examination regulations and module handbooks, universities often already speak in "areas," "pools," or "module packages." Module groups are the catalog counterpart to that thinking.

| Related area | Relationship |
|---|---|
| [Modules](/docs/fuxam-web/cms/academic-structure/modules) | Groups contain modules; each module still has its own versions, ECTS, and exams |
| [Manage module versions](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions) | Attaching modules to a group uses each module's **default version** |
| [Add modules to curriculum](/docs/fuxam-web/cms/academic-structure/curricula/add-modules-to-curriculum) | Curriculum items can reference a module group as organizational context while placing specific module versions |
| [Elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups) | Separate construct: election rules for optional modules inside a curriculum version |

## Module groups vs elective groups

These names sound similar; they solve different problems:

| | **Module group** | **Elective group** |
|---|---|---|
| **Where it lives** | Institution module catalog / campus management | A specific **curriculum version** structure |
| **Purpose** | Organize related modules for catalog and planning | Let students elect optional modules under rules |
| **Typical content** | Name, code, description, color, icon; attached modules | Election behavior (credit limits, course counts, unlock rules, timing) |
| **Student choice?** | No — organizational only | Yes — drives the **Elect Modules** experience |
| **Learn more** | This page | [Elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups) |

:::tip
A common pattern: keep a catalog **module group** such as "Economics Electives Pool," place those modules into a curriculum, then assign the optional ones to a curriculum **elective group** with "select until 12 ECTS" rules. The module group organizes the pool; the elective group governs student choice.
:::

## Key concepts

| Concept | Meaning |
|---|---|
| **Module group** | Named grouping of related modules (logical grouping used in curricula planning) |
| **Name** | Required label for the group (for example, Core Modules) |
| **Code** | Optional short identifier (for example, `CORE`) |
| **Description** | Optional text explaining the group's purpose |
| **Color / icon** | Optional visual styling so groups are easy to recognize in planning contexts |
| **Attached modules** | Modules included in the group; attachment resolves to each module's **default version** |

## What you can do with module groups

Institutions manage module groups through campus management operations (including integrations that sync academic structure). In plain terms, you can:

| Action | What it means |
|---|---|
| **List** | Browse module groups for your institution, optionally searching by name or related text |
| **Create** | Add a group with at least a **name**; optionally set code, description, color, and icon, and attach modules in the same step |
| **View** | Open a group to see its name, code, description, and styling |
| **Update** | Change group details and/or which modules are attached |
| **Delete** | Permanently remove the group record |

:::note
When you attach modules to a group, Fuxam uses each module's **default version**. Keep defaults accurate before bulk-attaching modules — see [Manage module versions](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions).
:::

## Create and manage module groups

### Create a group

1. Decide the group's purpose (for example, core modules shared across bachelor programs, or a methods pool).

2. Create the module group with a clear **name**. Add a **code** and **description** when your institution uses short identifiers in catalogs and reports.

3. Optionally set **color** and **icon** so the group is easy to spot in planning views.

4. Attach the relevant **modules**. Membership uses each module's default version — confirm defaults first if versions recently changed.

### Update membership or details

Update a group when the catalog changes: rename for clarity, adjust description after a handbook revision, or attach/detach modules as offerings move in or out of the pool. Prefer updating the group over creating near-duplicate groups with overlapping membership.

### Delete a group

Deleting a module group permanently removes the group record. Before deleting, confirm that curricula planning and staff workflows no longer rely on that grouping. Deleting a group does **not** delete the underlying modules or their versions — only the organizational grouping.

:::warning
Deletion is permanent for the group record. If you only need to stop using a pool temporarily, consider emptying membership or leaving the group unused rather than deleting it, unless your institution's process requires removal.
:::

## Worked example — core vs elective pool

**Institution catalog**

| Module group | Code | Attached modules (examples) |
|---|---|---|
| Core Modules | `CORE` | Introduction to Economics (`ECON101`), Academic Skills (`GEN100`) |
| Quantitative Methods | `QUANT` | Statistics (`STAT110`), Econometrics (`ECON210`) |

**Curriculum use**

1. Both groups help the program office see which catalog modules belong together.
2. In the B.A. curriculum, `ECON101` and `GEN100` are placed as **required** items (no elective group).
3. `STAT110` and `ECON210` are placed as optional items inside a curriculum [elective group](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups) with "Select until Credit Points = 12."
4. When Statistics moves from 5 to 6 ECTS, you [version the module](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions) and update the default — the Quantitative Methods module group still points at Statistics as a catalog member, while curricula and courses pick the correct version explicitly.

## Best practices

- Name groups after handbook language your faculty already uses (core, Wahlpflicht pool, methods area).
- Keep **codes** short and stable for reporting and integrations.
- Attach modules only after each has a sensible **default version** with correct ECTS.
- Do not use module groups as a substitute for [elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups) when students must choose under credit or count rules.
- Review group membership when you [archive modules](/docs/fuxam-web/cms/academic-structure/modules/archive-a-module) so retired units do not remain in pools that look current.

## Common pitfalls

- Confusing module groups with elective groups — one organizes the catalog; the other governs student election inside a curriculum.
- Attaching modules before setting the intended default version — membership resolves to defaults.
- Creating overlapping groups with nearly identical membership — prefer one clear pool per purpose.
- Expecting a module group to set ECTS or exams — those always live on the **module version**.

## FAQ

**Does a module group replace placing modules in a curriculum?**

No. You still [add module versions to a curriculum](/docs/fuxam-web/cms/academic-structure/curricula/add-modules-to-curriculum). The group helps organize related modules; curriculum items define program requirements.

**If I attach a module to a group, which version is used?**

Attachment uses the module's **default version**. Update the default when a new academic configuration should be preferred for new connections.

**Can students elect from a module group?**

Student election is configured with [elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups) on the curriculum. A module group alone does not define election rules.

**Does deleting a module group delete its modules?**

No. Only the group record is removed. Modules and their versions remain in the catalog.

## Related pages

**[Modules overview](/docs/fuxam-web/cms/academic-structure/modules)**

Identity, versions, ECTS, and how modules fit the Database.

**[Elective groups](/docs/fuxam-web/cms/academic-structure/curricula/elective-groups)**

Curriculum election rules for optional modules — distinct from module groups.

**[Add modules to curriculum](/docs/fuxam-web/cms/academic-structure/curricula/add-modules-to-curriculum)**

Place module versions into program structure.

**[Manage module versions](/docs/fuxam-web/cms/academic-structure/modules/manage-module-versions)**

Keep default versions accurate before attaching modules to groups.
