# 3. Path Templates & Reuse

User Type: **Training Institute**
Source: *Mi Digital Academy - Education CRM Features Document*

---

## 3. Path Templates & Reuse

### 3.1 Save Path as Template
**What it does:** Lets the Training Institute save a learning path as a reusable template: the Institute selects a published path, saves it as a template with a name and category, and the template captures the steps, sequence, and criteria. The Institute sees its templates. This enables reuse across cohorts.

**Sub-features:**
- Save a path as a template
- Template name and category
- Template captures steps, sequence, criteria
- Template list
- Edit a template
- Delete a template
- Templates available on web and mobile
- Templates event logging (saved, edited, deleted)
- Audit logging of the path template saving

**Training Institute User Journey:**
1. Training Institute opens the path templates.
2. Training Institute saves a path as a template.
3. Training Institute sets the template name and category.
4. The template captures the steps, sequence, and criteria.
5. The template list is shown.
6. Training Institute edits a template.
7. Training Institute opens Profile → "Activity" and confirms the templates events are recorded.

**Rules & Edge Cases:**
- A template is independent of the original path.
- Deleting a template does not affect existing paths.
- Templates events (saved, edited, deleted) are logged with the account and the timestamp.
- The path template saving is audit-logged with the account and the timestamp.

### 3.2 Create Path from Template
**What it does:** Lets the Training Institute create a new learning path from a template: the Institute selects a template, the path is pre-filled with the template's steps and criteria, and the Institute can adjust before publishing. The Institute sees the new path in its list. This speeds up path creation.

**Sub-features:**
- Create a path from a template
- Path pre-filled with template steps
- Adjust steps before publishing
- New path in the list
- Template source shown
- Multiple paths from one template
- Creation available on web and mobile
- Creation event logging (created from template)
- Audit logging of the path creation from template

**Training Institute User Journey:**
1. Training Institute opens the template creation.
2. Training Institute selects a template.
3. The path is pre-filled with the template steps.
4. Training Institute adjusts the steps before publishing.
5. The new path is in the list.
6. The template source is shown.
7. Training Institute opens Profile → "Activity" and confirms the creation events are recorded.

**Rules & Edge Cases:**
- A path created from a template is independent of the template.
- Multiple paths can be created from one template.
- Creation events (created from template) are logged with the account and the timestamp.
- The path creation from template is audit-logged with the account and the timestamp.

### 3.3 Clone & Duplicate Paths
**What it does:** Lets the Training Institute clone an existing learning path: the Institute selects a path, clones it with a new name, and the clone is a full copy of the steps, sequence, and criteria. The Institute can edit the clone independently. This supports quick variations of a path.

**Sub-features:**
- Clone an existing path
- Clone with a new name
- Full copy of steps, sequence, criteria
- Clone in the path list
- Edit the clone independently
- Clone source shown
- Cloning available on web and mobile
- Cloning event logging (cloned)
- Audit logging of the path cloning

**Training Institute User Journey:**
1. Training Institute opens the path cloning.
2. Training Institute selects a path.
3. Training Institute clones it with a new name.
4. The clone is a full copy of the steps, sequence, and criteria.
5. The clone is in the path list.
6. Training Institute edits the clone independently.
7. Training Institute opens Profile → "Activity" and confirms the cloning events are recorded.

**Rules & Edge Cases:**
- A clone is independent of the source path.
- Editing a clone does not affect the source.
- Cloning events (cloned) are logged with the account and the timestamp.
- The path cloning is audit-logged with the account and the timestamp.