# 6. Plan Configuration

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

---

## 6. Plan Configuration

### 6.1 Create, Edit, and Deactivate Plans
**What it does:** Manages the plan lifecycle: the Super Administrator creates a new plan (the name, the scope, the price, the period), edits an existing plan (the price, the scope, the features), and deactivates a plan (the plan is no longer offered, but the existing subscribers are handled). The plan lifecycle is the core of the membership management — the plans are the products, and their lifecycle is managed cleanly.

**Sub-features:**
- Plan creation: the plan created (the name, the scope, the price, the period)
- Plan edit: the plan edited (the price, the scope, the features)
- Plan deactivation: the plan deactivated (no longer offered)
- Deactivation handling: the existing subscribers handled (the grace, the migration)
- Plan list: the plans with their status (the active, the deactivated)
- Plan validation: the plan validated (the scope, the price, the period)
- Audit logging of the plan lifecycle

**Super Administrator User Journey:**
1. A new plan is needed. Super Admin creates the plan: the name, the scope (the subjects/courses), the price, and the period.
2. Validates the plan: the scope (the subjects/courses exist), the price (the price is set), and the period (the period is valid); the validation is the check.
3. Saves; the plan is live (the active status), and a learner can subscribe to it.
4. For a plan that needs an update (a price change, a scope change), Super Admin edits the plan (the price, the scope, the features); the change is recorded.
5. For a plan that is no longer offered (a discontinued plan), Super Admin deactivates it (the plan is no longer offered); the deactivation is recorded.
6. Handles the deactivation: the existing subscribers are handled (the grace period, the migration to a new plan); the subscribers are not dropped.
7. Reviews the plan list: the plans with their status (the active, the deactivated), so the plan state is visible.
8. The plan lifecycle is audit-logged with the plan, the action, and the timestamp.

**Rules & Edge Cases:**
- The plan creation is the name, the scope, the price, and the period; the plan is the product.
- The plan edit is the price, the scope, and the features; the change is recorded.
- The plan deactivation is the no-longer-offered status; the existing subscribers are handled (the grace, the migration).
- A deactivated plan is not offered (the new subscribers cannot subscribe); the existing subscribers are handled.
- The plan list shows the status (the active, the deactivated); the plan state is visible.
- Plan lifecycle is audit-logged with the plan, action, and timestamp.

### 6.2 Define Features and Limits per Plan (e.g., AI Assistant Question Limits)
**What it does:** Defines the features and limits per plan: the Super Administrator sets the features each plan includes (the content access, the AI assistant, the mentorship) and the limits (the AI assistant question limit, the download cap, the concurrent users), so the plans are differentiated by the features and the limits. The limits are the plan's boundaries — the free plan has the low limit, the premium plan has the high limit.

**Sub-features:**
- Feature definition: the features per plan (the content access, the AI assistant, the mentorship)
- Limit definition: the limits per plan (the AI assistant question limit, the download cap, the concurrent users)
- Feature scope: the features the plan includes (the plan's scope)
- Limit scope: the limits the plan has (the plan's boundaries)
- Plan differentiation: the plans differentiated by the features and the limits (the free vs. the premium)
- Limit enforcement: the limits enforced (the AI assistant question limit, the download cap)
- Audit logging of the feature/limit definition

**Super Administrator User Journey:**
1. For a plan, Super Admin defines the features: the content access (the subjects/courses), the AI assistant (the access), and the mentorship (the sessions); the features are the plan's scope.
2. Defines the limits: the AI assistant question limit (the questions per day), the download cap (the downloads per month), and the concurrent users (the devices); the limits are the plan's boundaries.
3. Sets the plan differentiation: the free plan has the low limit (the 5 AI questions per day), the premium plan has the high limit (the 50 AI questions per day); the differentiation is the value.
4. Saves; the features and limits are live, and the plan is differentiated (the free vs. the premium).
5. The limits are enforced: the AI assistant question limit (the 5 questions per day for the free plan), the download cap (the 10 downloads per month); the enforcement is the boundary.
6. For a limit breach (the AI assistant question limit reached), the learner is notified (the limit reached, the upgrade prompt); the limit is the upgrade trigger.
7. For a feature/limit change (a new feature, a new limit), Super Admin re-defines the plan (the new feature, the new limit); the change is recorded.
8. The feature/limit definition is audit-logged with the plan, the features, the limits, and the timestamp.

**Rules & Edge Cases:**
- The feature definition is the features per plan (the content access, the AI assistant, the mentorship); the features are the plan's scope.
- The limit definition is the limits per plan (the AI assistant question limit, the download cap, the concurrent users); the limits are the plan's boundaries.
- The plan differentiation is by the features and the limits (the free vs. the premium); the differentiation is the value.
- The limit enforcement is the boundary (the AI assistant question limit, the download cap); the enforcement is the limit.
- A limit breach (the AI assistant question limit reached) triggers the notification (the limit reached, the upgrade prompt); the limit is the upgrade trigger.
- Feature/limit definition is audit-logged with the plan, features, limits, and timestamp.

### 6.3 Plan Visibility and Availability Control
**What it does:** Controls the plan visibility and availability: the Super Administrator sets which plans are visible (shown to the learners) and which are available (can be subscribed to), so the plans are controlled (the hidden plan is not shown, the unavailable plan cannot be subscribed to). The visibility and availability are the plan's exposure — the plan is visible but not available (the coming soon), or available but not visible (the internal plan).

**Sub-features:**
- Plan visibility: the plans shown to the learners (the visible plans)
- Plan availability: the plans that can be subscribed to (the available plans)
- Visibility control: the visibility set (the visible, the hidden)
- Availability control: the availability set (the available, the unavailable)
- Plan state: the plan's state (the visible and available, the visible but unavailable, the hidden but available)
- State change: the state changed (the visibility, the availability)
- Audit logging of the state changes

**Super Administrator User Journey:**
1. For a plan, Super Admin sets the visibility: the plan is shown to the learners (the visible) or not (the hidden); the visibility is the exposure.
2. Sets the availability: the plan can be subscribed to (the available) or not (the unavailable); the availability is the subscription.
3. Sets the plan state: the visible and available (the normal plan), the visible but unavailable (the coming soon), or the hidden but available (the internal plan); the state is the control.
4. Saves; the state is live, and the plan's exposure is controlled (the visible is shown, the available is subscribed).
5. For a state change (a plan made visible, a plan made available), Super Admin changes the state (the visibility, the availability); the change is recorded.
6. For a plan that is visible but unavailable (the coming soon), the learners see it (the plan is shown) but cannot subscribe (the subscription is disabled); the state is the control.
7. Reviews the plan states: the plans with their state (the visible and available, the visible but unavailable, the hidden but available), so the plan exposure is visible.
8. The state changes are audit-logged with the plan, the state, and the timestamp.

**Rules & Edge Cases:**
- The plan visibility is the shown to the learners (the visible plans); the visibility is the exposure.
- The plan availability is the can be subscribed to (the available plans); the availability is the subscription.
- The plan state is the visible and available, the visible but unavailable, or the hidden but available; the state is the control.
- A state change (the visibility, the availability) is recorded (the change, the time); it is auditable.
- A visible but unavailable plan (the coming soon) is shown but not subscribed; the state is the control.
- State changes are audit-logged with the plan, state, and timestamp.