---
title: Assignment priority
description: >-
  How Fuxam resolves which academic ruleset applies to each student — user,
  cohort, and study program assignments, fallbacks, and what the effective
  ruleset controls.
sidebar:
  order: 5
  hidden: true
---

When multiple ruleset assignments could apply to a student, Fuxam uses a fixed **assignment priority** order to pick one **effective ruleset**. That ruleset's version settings — attempt limits, grading schema, weights, credit points, deadlines — govern the student's exams and study plan.

Priority is the institutional answer to a classic regulations problem: general program rules, cohort-specific intakes, and individual exceptions cannot all win at once. A transparent hierarchy keeps examiners, program staff, and students looking at the same policy bundle.

How that effective ruleset shapes resits and permanent failure is covered in [How exam attempts work](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/attempt-lifecycle) and [Configure attempt limits](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/configure-attempt-limits).

## Why it matters

Without a documented resolution order, universities invent local workarounds — sticky notes, parallel spreadsheets, or conflicting "special cases" that never reach the Exam Center. Assignment priority makes exceptions first-class:

- **Study program** assignments encode the default *Prüfungsordnung* for everyone on that program
- **Cohort** assignments override for a specific intake (for example, a transitional regulation year)
- **User** assignments encode board decisions, [disability compensation](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/disability-compensation-and-hardship), hardship, or documented individual study agreements

Getting priority wrong is one of the most common causes of "why does this student have different attempt tabs?" tickets.

Assignments are created on a ruleset version's **Connections** (or via **Campus Management → Programs → Users**). Resolution runs whenever Fuxam needs the student's effective policy for attempts, schemas, weights, and related deadlines — including when building attempt eligibility in [My Exams](/docs/fuxam-web/cms/exams-and-reporting/my-exams).

:::info
This priority applies to **ruleset resolution** — which policy bundle is active for a student. It is separate from the **examinee assignment mode** on exam types, which controls how exam responsibles are assigned to students.
:::

## Priority order

Fuxam resolves the effective ruleset in this order (first match wins):

| Priority | Assignment source | Description |
|---|---|---|
| **1 (highest)** | **User** | Direct assignment on the individual student |
| **2** | **Cohort** | Assignment on the student's cohort |
| **3** | **Study program** | Assignment on the student's study program |
| **4 (default)** | **None** | Built-in defaults (for example, 3 passed / 3 failed attempts) |

A direct user assignment always overrides cohort and study program assignments. A cohort assignment overrides study program only.

## Key concepts

| Term | Meaning |
|------|---------|
| **Effective ruleset** | The single winning policy bundle for a student after priority resolution |
| **Connection / assignment** | Link from a ruleset version to a program, cohort, or user |
| **Fallback** | After removing a higher-priority assignment, the next level down becomes effective |
| **Bulk assign** | Toolbar actions on Programs → Users for many students at once |
| **Rule priority (domain)** | Academic idea that more specific decisions override general regulations — mirrored here as user → cohort → program |

## Worked examples

### Example 1 — Program default, cohort override

| Level | Assignment | Max failed attempts |
|-------|------------|---------------------|
| Study program | Ruleset "PO 2024" | 3 |
| Cohort 2023 (legacy intake) | Ruleset "PO 2020 transitional" | 2 |
| User | none | — |

Students in cohort 2023 see **max failed = 2**. Students in other cohorts on the same program see **max failed = 3**.

### Example 2 — Individual board exception

Same program as above (max failed 3). One student receives a documented decision allowing an additional failure. Staff assign a user-level ruleset version with **Maximum failed attempts** = 4.

That student resolves to the **user** ruleset regardless of cohort or program. When the exception ends, remove the user assignment so the confirmation dialog's fallback (cohort or program) takes over.

### Example 3 — Forgotten user assignment

Symptom: One student always shows different attempt usage (for example, "1/4" while peers show "1/3"). Check **Campus Management → Programs → Users** → **Academic ruleset** column. An obsolete user assignment is the usual cause.

### Example 4 — Disability compensation with higher failed ceiling

A board grants one extra failed attempt under *Nachteilsausgleich*-related hardship. Create or reuse a narrowly scoped ruleset version with a higher **Maximum failed attempts**, assign it at **user** priority, and keep the program ruleset unchanged for peers. See [Disability compensation and hardship](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/disability-compensation-and-hardship).

:::tip
Treat user-level rulesets like individual regulatory decisions: require a reference in the case file, and schedule a review date to remove the assignment when the exception expires.
:::

## Where to assign rulesets

### Ruleset version connections

On a ruleset version page (**Settings → Campus Management → Academic Rulesets → [ruleset] → [version]**), use the connections section to link the version to:

- Study programs
- Cohorts
- Individual users

Replacing an existing assignment on an entity overwrites the previous ruleset link for that entity.

### Study program users table

In **Campus Management → Programs → Users**, the **Academic ruleset** column shows each student's effective ruleset. Click the cell to assign a ruleset directly to a user — this creates a priority-1 user assignment.

Bulk assign and bulk remove actions are available from the toolbar when managing many students.

## What assignment priority controls

The effective ruleset determines:

- **Module attempt limits** — max passed and failed attempts ([Configure attempt limits](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/configure-attempt-limits); lifecycle in [How exam attempts work](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/attempt-lifecycle))
- **Grading schema** — which rating scale applies to graded exams
- **Grade weights** — module vs. final grade weighting ([Grade weighting](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/grade-weighting))
- **Credit-point requirements** and exam-related deadlines ([Credit-point requirements](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/credit-point-requirements); [Appointment and withdrawal deadlines](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/appointment-and-withdrawal-deadlines))
- **Custom policy fields** defined on the ruleset version

It does **not** replace [LMS course grading](/docs/fuxam-web/lms/grading) inside a learning journey; it governs formal CMS academic policy for the student's exams and related study-plan settings.

## Removing a user assignment

When you remove a direct user assignment, the student **falls back** to the cohort ruleset (if any), then the study program ruleset, then defaults. The confirmation dialog shows which ruleset will become effective after removal.

:::warning
Always read the fallback shown in the confirmation dialog before removing a user assignment — especially if the cohort and program point at different regulation years. A fallback that changes max failed from 4 to 2 can immediately affect permanent-failure eligibility.
:::

## How to assign a ruleset with correct priority

1. For program-wide policy, assign the ruleset version to the **study program** on the version connections page.

2. For cohort-specific overrides, assign to the **cohort** — this takes priority over the study program assignment for students in that cohort.

3. For individual exceptions, assign directly to the **user** from the ruleset version page or the Programs → Users table — this takes priority over all other assignments.

4. Verify the effective ruleset in the Programs → Users academic ruleset column for sample students.

## Best practices

- **Default at program level** — one ruleset version per regulation generation for the study program.
- **Cohort only when the intake truly differs** — transitional years, pilot rules, or continuing-education intakes.
- **User assignments need a paper trail** — treat them like individual regulatory decisions, and remove them when the exception ends so fallback restores the cohort or program rule.
- **Verify with samples** after every bulk change — one student per assignment level is enough to catch inverted expectations.
- **Do not confuse with examiner assignment** — exam-type examinee modes are a different concept from ruleset priority.
- **Check attempt tabs after reassignment** — effective limits change what [My Exams](/docs/fuxam-web/cms/exams-and-reporting/my-exams) shows for eligibility and usage.

## Common pitfalls

| Pitfall | Symptom | Remedy |
|---------|---------|--------|
| Updating only the program ruleset | Cohort students unchanged | Check for cohort connections |
| Forgotten user exception | One student always differs | Inspect Academic ruleset column; remove user assignment if obsolete |
| Overwriting connections casually | Previous ruleset link disappears for that entity | Replacing an assignment overwrites — confirm before save |
| Assuming LMS grades follow the ruleset | Course marks look "out of policy" | LMS grading is separate; formal limits live in CMS rulesets |
| Expecting priority to change exam-type workflow | Attempt 3 still missing under reassessment | Workflow is on the [exam type](/docs/fuxam-web/cms/exams-and-reporting/exam-types); priority only picks the ruleset numbers |

## FAQ

**What happens if nothing is assigned?**

Fuxam uses built-in defaults (for example, 3 passed / 3 failed attempts). Other grading configuration from a ruleset will not apply until an assignment exists.

**Does a cohort assignment affect students outside that cohort?**

No. Cohort assignments apply to students in that cohort only, and only when those students do not have a higher-priority user assignment.

**Is this the same as assigning exam responsibles?**

No. Ruleset assignment priority chooses the **policy bundle**. Examinee assignment mode on exam types controls how **exam responsibles** map to students — a separate mechanism.

**Where do I see the effective ruleset quickly?**

In **Campus Management → Programs → Users**, the **Academic ruleset** column shows each student's effective ruleset.

**Can a user assignment change permanent-failure outcomes?**

Yes. Because the effective ruleset supplies max failed attempts, a user-level ceiling that differs from the program rule can change when a student becomes permanently failed. See [How exam attempts work](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/attempt-lifecycle).

## Related pages

- [How exam attempts work](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/attempt-lifecycle) — how the effective ruleset shapes the attempt lifecycle
- [Create a ruleset](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/create-a-ruleset) — create a ruleset before assigning it
- [Configure attempt limits](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/configure-attempt-limits) — how resolved rulesets cap module attempts
- [Disability compensation and hardship](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/disability-compensation-and-hardship) — typical uses of user-level assignments
- [Academic rulesets](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets) — overview of ruleset concepts
- [Edit a ruleset](/docs/fuxam-web/cms/exams-and-reporting/academic-rulesets/edit-a-ruleset) — connections and grading configuration on a version
