# 5. Bulk License Packages

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

---

## 5. Bulk License Packages

### 5.1 Tiered Pricing (10-50, 51-200, 201-500, 500+ Licenses)
**What it does:** Provides the tiered pricing for bulk licenses: the license packages are priced by the license count tier (the 10-50, the 51-200, the 201-500, the 500+), so an institute (or an enterprise) gets a better price per license as the count increases. The Super Administrator defines the tiers (the count range, the price per license) so the bulk pricing is structured and the volume is rewarded.

**Sub-features:**
- License tiers: the count tiers (the 10-50, the 51-200, the 201-500, the 500+)
- Tier pricing: the price per license per tier (the price decreases with the tier)
- Tier definition: the tiers defined by the Super Admin (the count range, the price per license)
- Tier assignment: the license count assigned to a tier (the count determines the tier)
- Tier pricing application: the price applied (the license count, the tier, the price per license)
- Tier record: the tier recorded (the institute, the count, the tier, the price)
- Audit logging of the tier definition and the applications

**Super Administrator User Journey:**
1. Super Admin defines the license tiers: the count ranges (the 10-50, the 51-200, the 201-500, the 500+) and the price per license per tier (the price decreases with the tier).
2. Sets the tier pricing: the price per license per tier (the volume is rewarded, the larger the tier, the lower the price per license); the tiers are explicit.
3. Saves; the tiers are live, and an institute can buy the bulk licenses (the count determines the tier).
4. An institute buys the bulk licenses (the count, e.g., 150); the count is assigned to the tier (the 51-200), and the price per license is the tier's price.
5. The tier is recorded: the institute, the count, the tier, and the price; the record is the proof.
6. For an institute that increases the count (a new tier), the price per license is re-applied (the new tier, the new price); the change is recorded.
7. Reviews the bulk licenses: the count, the tiers, the prices, so the bulk demand is visible.
8. The tier definition and the applications are audit-logged with the tier, the institute, and the timestamp.

**Rules & Edge Cases:**
- The license tiers are the count ranges (the 10-50, the 51-200, the 201-500, the 500+); the count determines the tier.
- The tier pricing is the price per license per tier (the price decreases with the tier); the volume is rewarded.
- A tier assignment is the count to the tier (the count determines the tier); the assignment is explicit.
- A count increase (a new tier) re-applies the price (the new tier, the new price); the change is recorded.
- A tier adjustment (the count range, the price per license) is recorded (the change, the time); it is auditable.
- Tier definition and applications are audit-logged with the tier, institute, and timestamp.

### 5.2 Custom Enterprise Pricing
**What it does:** Provides the custom enterprise pricing: for the large enterprises (the 500+ licenses, or the special cases), the pricing is custom (negotiated, not the standard tier), so the enterprise gets a price that fits its scale and its terms. The Super Administrator defines the custom pricing (the enterprise, the count, the price, the terms) so the enterprise deal is structured and the custom terms are recorded.

**Sub-features:**
- Custom pricing: the pricing for the enterprise (the count, the price, the terms)
- Enterprise scope: the enterprise's scope (the licenses, the features, the support)
- Custom terms: the terms (the payment, the duration, the support)
- Pricing definition: the pricing defined by the Super Admin (the enterprise, the count, the price, the terms)
- Pricing application: the pricing applied (the enterprise's price is the custom price)
- Pricing record: the pricing recorded (the enterprise, the count, the price, the terms)
- Audit logging of the pricing definition and the applications

**Super Administrator User Journey:**
1. An enterprise requests the bulk licenses (the count, e.g., 1000). Super Admin defines the custom pricing (the count, the price, the terms).
2. Sets the enterprise scope: the licenses, the features, and the support (the enterprise's scope); the scope is explicit.
3. Sets the custom terms: the payment (the schedule), the duration (the term), and the support (the level); the terms are the deal.
4. Saves; the custom pricing is live, and the enterprise's price is the custom price (per the terms).
5. The enterprise buys the bulk licenses (the count, the custom price); the pricing is applied (the enterprise's price is the custom price).
6. The pricing is recorded: the enterprise, the count, the price, and the terms; the record is the proof.
7. For an enterprise that changes the terms (a new duration, a new support level), the pricing is re-applied (the new terms, the new price); the change is recorded.
8. The pricing definition and the applications are audit-logged with the pricing, the enterprise, and the timestamp.

**Rules & Edge Cases:**
- The custom pricing is for the enterprise (the count, the price, the terms); it is negotiated, not the standard tier.
- The enterprise scope is the licenses, the features, and the support; the scope is explicit.
- The custom terms are the payment, the duration, and the support; the terms are the deal.
- A terms change (a new duration, a new support level) re-applies the pricing (the new terms, the new price); the change is recorded.
- A pricing adjustment (the count, the price, the terms) is recorded (the change, the time); it is auditable.
- Pricing definition and applications are audit-logged with the pricing, enterprise, and timestamp.

### 5.3 Volume Discounts
**What it does:** Provides the volume discounts for the bulk licenses: the discount for the license count (the more licenses, the greater the discount), so the institute (or the enterprise) gets a better price per license as the count increases. The Super Administrator defines the volume discounts (the count, the discount) so the bulk pricing rewards the volume and the discount is explicit.

**Sub-features:**
- Volume discount: the discount for the license count (the more licenses, the greater the discount)
- Count: the license count (the discount key)
- Discount: the discount (the percentage, the amount)
- Discount definition: the discount defined by the Super Admin (the count, the discount)
- Discount application: the discount applied (the institute's price is the discounted price)
- Discount record: the discount recorded (the institute, the count, the discount)
- Audit logging of the discount definition and the applications

**Super Administrator User Journey:**
1. Super Admin defines the volume discounts: the license count (the count) and the discount (the percentage, the amount); the discount is the incentive.
2. Sets the discount tiers: the count tiers (the 10-50, the 51-200, etc.) and the discount per tier; the tiers are explicit.
3. Saves; the discounts are live, and an institute's price is the discounted price (per the count).
4. An institute buys the bulk licenses (the count, e.g., 300); the discount is applied (the institute's price is the discounted price, per the count).
5. The discount is recorded: the institute, the count, and the discount; the record is the proof.
6. For an institute that increases the count (a new tier), the discount is re-applied (the new count, the new discount); the change is recorded.
7. Reviews the volume discounts: the count, the counts, the discounts, so the volume discount is visible.
8. The discount definition and the applications are audit-logged with the discount, the institute, and the timestamp.

**Rules & Edge Cases:**
- The volume discount is for the license count (the more licenses, the greater the discount); the discount is the incentive.
- The count is the discount key (the license count); the discount is per the count.
- The discount tiers are explicit (the count tiers, the discount per tier); the tiers are the structure.
- A count increase (a new tier) re-applies the discount (the new count, the new discount); the change is recorded.
- A discount adjustment (the count, the discount) is recorded (the change, the time); it is auditable.
- Discount definition and applications are audit-logged with the discount, institute, and timestamp.

### 5.4 Dedicated Account Manager
**What it does:** Provides the dedicated account manager: the bulk license customer (the institute, the enterprise) is assigned a dedicated account manager (the single point of contact for the account), so the customer has a named person for the account (the support, the issues, the changes). The Super Administrator assigns the account manager (the person, the account) so the customer's relationship is personal and the account is managed.

**Sub-features:**
- Account manager: the dedicated person for the account (the single point of contact)
- Assignment: the account manager assigned to the account (the person, the account)
- Manager scope: the manager's scope (the support, the issues, the changes)
- Manager contact: the manager's contact (the email, the phone)
- Manager handoff: the manager changed (the handoff, the continuity)
- Manager record: the assignment recorded (the account, the manager, the time)
- Audit logging of the assignment

**Super Administrator User Journey:**
1. A bulk license customer (the institute, the enterprise) is onboarded. Super Admin assigns the dedicated account manager (the person, the account).
2. Sets the manager scope: the support, the issues, and the changes (the manager's scope); the scope is explicit.
3. Sets the manager contact: the email and the phone (the manager's contact); the customer knows who to reach.
4. Saves; the assignment is live, and the customer has the named account manager (the single point of contact).
5. The customer reaches the account manager (the support, the issue, the change); the manager handles it (the account is managed).
6. For a manager change (a handoff), Super Admin re-assigns the account manager (the new person, the account); the handoff is the continuity.
7. Reviews the account managers: the accounts, the managers, the scope, so the account management is visible.
8. The assignment is audit-logged with the account, the manager, and the timestamp.

**Rules & Edge Cases:**
- The account manager is the dedicated person for the account (the single point of contact); the relationship is personal.
- The assignment is the person to the account (the person, the account); it is explicit.
- The manager scope is the support, the issues, and the changes; the scope is the manager's responsibility.
- A manager change (a handoff) is re-assigned (the new person, the account); the handoff is the continuity.
- An assignment change is recorded (the change, the time); it is auditable.
- Assignment is audit-logged with the account, manager, and timestamp.

### 5.5 Custom Branding Options
**What it does:** Provides the custom branding options: the bulk license customer (the institute, the enterprise) can brand the platform with its own identity (the logo, the colors, the name), so the learners see the customer's brand, not the platform's. The Super Administrator enables the custom branding (the logo, the colors, the name) so the customer's identity is on the platform and the branding is consistent.

**Sub-features:**
- Custom branding: the customer's brand on the platform (the logo, the colors, the name)
- Brand elements: the logo, the colors, and the name (the customer's identity)
- Branding scope: the branding on the platform (the learner's view, the customer's brand)
- Branding setup: the branding set (the customer provides the elements, the Super Admin applies them)
- Branding consistency: the branding consistent (the elements match, the view is uniform)
- Branding record: the branding recorded (the customer, the elements, the time)
- Audit logging of the branding setup

**Super Administrator User Journey:**
1. A bulk license customer (the institute, the enterprise) requests the custom branding. Super Admin enables the custom branding (the logo, the colors, the name).
2. The customer provides the brand elements (the logo, the colors, the name); the Super Admin applies them (the branding is set).
3. Sets the branding scope: the branding on the platform (the learner's view, the customer's brand); the scope is explicit.
4. Saves; the branding is live, and the learners see the customer's brand (the logo, the colors, the name).
5. For a branding change (a new logo, a new color), the customer provides the new elements; the Super Admin applies them (the change is recorded).
6. Reviews the branding consistency: the elements match (the logo, the colors, the name), and the view is uniform (the branding is consistent); the consistency is the quality.
7. Reviews the custom branding: the customers, the elements, the scope, so the branding is visible.
8. The branding setup is audit-logged with the customer, the elements, and the timestamp.

**Rules & Edge Cases:**
- The custom branding is the customer's brand on the platform (the logo, the colors, the name); the identity is the customer's.
- The brand elements are the logo, the colors, and the name; the elements are the identity.
- The branding scope is the platform (the learner's view, the customer's brand); the scope is explicit.
- A branding change (a new logo, a new color) is re-applied (the new elements, the change recorded); it is auditable.
- The branding consistency is the elements match (the logo, the colors, the name), and the view is uniform; the consistency is the quality.
- Branding setup is audit-logged with the customer, elements, and timestamp.

### 5.6 Priority Support
**What it does:** Provides the priority support: the bulk license customer (the institute, the enterprise) gets the priority support (the faster response, the dedicated channel), so the customer's issues are handled with the priority (the SLA is the priority). The Super Administrator enables the priority support (the SLA, the channel) so the customer's support is the priority and the response is fast.

**Sub-features:**
- Priority support: the support for the customer (the faster response, the dedicated channel)
- SLA: the service level (the response time, the resolution time)
- Support channel: the dedicated channel (the email, the phone, the portal)
- Support setup: the support set (the SLA, the channel)
- Support handling: the support handled (the issue, the response, the resolution)
- Support record: the support recorded (the customer, the issue, the response, the time)
- Audit logging of the support setup and the handling

**Super Administrator User Journey:**
1. A bulk license customer (the institute, the enterprise) is onboarded. Super Admin enables the priority support (the SLA, the channel).
2. Sets the SLA: the response time and the resolution time (the service level); the SLA is the priority.
3. Sets the support channel: the dedicated channel (the email, the phone, the portal); the channel is the customer's.
4. Saves; the priority support is live, and the customer's issues are handled with the priority (the SLA is met).
5. The customer raises an issue (the support, the problem); the support is handled (the response, the resolution) per the SLA.
6. The support is recorded: the customer, the issue, the response, and the time; the record is the proof.
7. For an SLA breach (a response time exceeded), the Super Admin is alerted (the breach flagged); the issue is escalated (the priority is restored).
8. The support setup and the handling are audit-logged with the customer, the support, and the timestamp.

**Rules & Edge Cases:**
- The priority support is the support for the customer (the faster response, the dedicated channel); the priority is the SLA.
- The SLA is the service level (the response time, the resolution time); the SLA is the priority.
- The support channel is the dedicated channel (the email, the phone, the portal); the channel is the customer's.
- An SLA breach (a response time exceeded) triggers the alert (the breach flagged); the issue is escalated (the priority is restored).
- A support change (a new SLA, a new channel) is re-applied (the new terms, the change recorded); it is auditable.
- Support setup and handling are audit-logged with the customer, support, and timestamp.

### 5.7 Custom Reporting
**What it does:** Provides the custom reporting: the bulk license customer (the institute, the enterprise) gets the custom reports (the reports for the customer's needs, the metrics, the format), so the customer sees the data it needs (the usage, the progress, the financials). The Super Administrator enables the custom reporting (the reports, the metrics, the format) so the customer's reporting is tailored and the data is the customer's.

**Sub-features:**
- Custom reporting: the reports for the customer (the metrics, the format)
- Report scope: the reports' scope (the usage, the progress, the financials)
- Report definition: the reports defined (the metrics, the format, the frequency)
- Report generation: the reports generated (the data, the format)
- Report delivery: the reports delivered (the email, the portal, the export)
- Report record: the reports recorded (the customer, the reports, the time)
- Audit logging of the report definition and the generation

**Super Administrator User Journey:**
1. A bulk license customer (the institute, the enterprise) requests the custom reporting. Super Admin enables the custom reporting (the reports, the metrics, the format).
2. Sets the report scope: the usage, the progress, and the financials (the reports' scope); the scope is explicit.
3. Sets the report definition: the metrics, the format, and the frequency (the reports defined); the definition is the structure.
4. Saves; the custom reporting is live, and the reports are generated (the data, the format) per the definition.
5. The reports are delivered (the email, the portal, the export); the customer receives them (the data is the customer's).
6. The reports are recorded: the customer, the reports, and the time; the record is the proof.
7. For a report change (a new metric, a new format), the Super Admin re-defines the report (the new metric, the new format); the change is recorded.
8. The report definition and the generation are audit-logged with the customer, the reports, and the timestamp.

**Rules & Edge Cases:**
- The custom reporting is the reports for the customer (the metrics, the format); the reporting is tailored.
- The report scope is the usage, the progress, and the financials; the scope is explicit.
- The report definition is the metrics, the format, and the frequency; the definition is the structure.
- A report change (a new metric, a new format) is re-defined (the new metric, the new format); the change is recorded.
- The report delivery is the email, the portal, and the export; the delivery is the customer's.
- Report definition and generation are audit-logged with the customer, reports, and timestamp.