# 1. Career Path Definitions

User Type: **Super Administrator**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 1. Career Path Definitions

### 1.1 Career Path Catalog
**What it does:** The Super Admin manages the catalog of career paths so learners can be guided toward defined career outcomes.

**Sub-features:**
- Path creation: the creation of a career path
- Path details: the title, description, and industry of the path
- Path prerequisites: the skills and qualifications required
- Path outcomes: the roles and outcomes the path leads to
- Path catalog: the catalog of all defined career paths
- Available on web
- Event logging (action performed)
- Audit logging of career path definitions

**Super Admin User Journey:**
1. As a Super Admin, open the career path catalog.
2. Create a new career path with title, description, and industry.
3. Define the prerequisites and outcomes.
4. Save the path and verify it appears in the catalog.

**Rules & Edge Cases:**
- A path creation requires a title and description.
- A path details includes the industry classification.
- A path prerequisites lists the required skills and qualifications.
- A path outcomes lists the roles the path leads to.
- A path catalog lists all defined paths.
- A path with no prerequisites is open to all learners.
- Path actions are audit-logged with the actor and timestamp.

### 1.2 Path Structure
**What it does:** The Super Admin defines the structure of a career path so the learning sequence toward the path is clear.

**Sub-features:**
- Stage definition: the stages within the path
- Stage ordering: the sequence of the stages
- Stage milestones: the milestones within each stage
- Stage duration: the expected duration per stage
- Structure preview: the preview of the path structure
- Available on web
- Event logging (action performed)
- Audit logging of path structure

**Super Admin User Journey:**
1. As a Super Admin, open the path structure editor.
2. Define the stages and their order.
3. Set the milestones and duration per stage.
4. Preview the structure and save.

**Rules & Edge Cases:**
- A stage definition requires a name and description.
- A stage ordering defines the sequence of the stages.
- A stage milestone marks a checkpoint within the stage.
- A stage duration is the expected time to complete the stage.
- A structure preview shows the full path flow.
- A path with no stages cannot be recommended.
- Structure changes are audit-logged with the actor and timestamp.

### 1.3 Path Requirements
**What it does:** The Super Admin sets the requirements for a career path so learners know what is needed to pursue it.

**Sub-features:**
- Skill requirements: the skills required for the path
- Course requirements: the courses required for the path
- Assessment requirements: the assessments required for the path
- Requirement levels: the proficiency level per requirement
- Requirement checklist: the checklist of requirements
- Available on web
- Event logging (action performed)
- Audit logging of path requirements

**Super Admin User Journey:**
1. As a Super Admin, open the path requirements editor.
2. Add the skill, course, and assessment requirements.
3. Set the proficiency level per requirement.
4. Review the requirement checklist and save.

**Rules & Edge Cases:**
- A skill requirement names a skill and its level.
- A course requirement links a course to the path.
- An assessment requirement links an assessment to the path.
- A requirement level is the proficiency needed (basic, intermediate, advanced).
- A requirement checklist lists all requirements with status.
- A requirement with no level defaults to basic.
- Requirement changes are audit-logged with the actor and timestamp.

### 1.4 Path Enablement
**What it does:** The Super Admin enables or disables career paths so only active paths are available for guidance.

**Sub-features:**
- Path activation: the path toggled active or inactive
- Path deactivation: the path disabled from guidance
- Effective date: the date the enablement takes effect
- Enablement scope: the institutes the path applies to
- Enablement status: the current status of the path
- Available on web
- Event logging (action performed)
- Audit logging of path enablement

**Super Admin User Journey:**
1. As a Super Admin, open the path enablement.
2. Activate or deactivate the path.
3. Set the effective date and scope.
4. Verify the enablement status.

**Rules & Edge Cases:**
- A path activation makes the path available for guidance.
- A path deactivation removes the path from guidance.
- An effective date schedules the enablement change.
- An enablement scope limits the path to specific institutes.
- An enablement status reflects the current state.
- A deactivated path is not shown to learners.
- Enablement changes are audit-logged with the actor and timestamp.

### 1.5 Path Versioning
**What it does:** The Super Admin versions career paths so changes are tracked and previous versions are preserved.

**Sub-features:**
- Version creation: the creation of a new path version
- Version history: the history of path versions
- Version comparison: the comparison between versions
- Version rollback: the rollback to a previous version
- Version notes: the notes describing each version
- Available on web
- Event logging (action performed)
- Audit logging of path versioning

**Super Admin User Journey:**
1. As a Super Admin, open the path versioning.
2. Create a new version with notes.
3. Compare versions and review the history.
4. Roll back to a previous version if needed.

**Rules & Edge Cases:**
- A version creation snapshots the current path state.
- A version history lists all versions chronologically.
- A version comparison shows the differences between two versions.
- A version rollback restores a previous version.
- A version note describes the change in the version.
- A rollback creates a new version, not a deletion.
- Version actions are audit-logged with the actor and timestamp.