# 2. Branding Assets Management

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

---

## 2. Branding Assets Management

### 2.1 Logo and Asset Upload
**What it does:** The Super Admin uploads and manages the branding assets (logos, images, icons) used across the white-label surfaces.

**Sub-features:**
- Asset upload: the upload of logos, images, and icons
- Asset types: the asset types supported (logo, favicon, banner, icon)
- Asset format: the allowed formats and size limits per asset type
- Asset replacement: the replacement of an existing asset
- Asset deletion: the deletion of an unused asset
- Available on web
- Event logging (action performed)
- Audit logging of logo and asset upload

**Super Admin User Journey:**
1. As a Super Admin, open the branding assets management.
2. Upload the institute logo, favicon, and banner.
3. Replace an existing asset where needed.
4. Delete an unused asset.
5. Verify the assets are applied across the branded surfaces.

**Rules & Edge Cases:**
- An asset must be in an allowed format for its type.
- An asset exceeding the size limit for its type is rejected.
- An asset replacement keeps the same slot; the old asset is versioned.
- An asset in use cannot be deleted; it must be replaced first.
- An asset upload is validated for integrity before acceptance.
- An asset is scoped to the institute that uploaded it.
- Upload actions are audit-logged with the actor and timestamp.

### 2.2 Color Palette Management
**What it does:** The Super Admin manages the institute's color palette so all branded surfaces use a consistent set of colors.

**Sub-features:**
- Palette definition: the definition of the brand color palette
- Palette roles: the role per color (primary, secondary, accent, success, warning, error)
- Palette preview: the preview of the palette on sample surfaces
- Palette import: the import of a palette from a file
- Palette export: the export of the palette for reuse
- Available on web
- Event logging (action performed)
- Audit logging of color palette management

**Super Admin User Journey:**
1. As a Super Admin, open the color palette management.
2. Define the palette colors and assign roles.
3. Preview the palette on sample surfaces.
4. Import or export the palette as needed.
5. Save and verify the palette is applied across the branded surfaces.

**Rules & Edge Cases:**
- A palette role must be assigned to exactly one color.
- A palette color is stored as a hex value.
- A palette preview renders the colors on sample UI elements.
- A palette import must match the expected schema.
- A palette export produces a file in the selected format.
- A palette change applies to all branded surfaces on the next load.
- Palette changes are audit-logged with the actor and timestamp.

### 2.3 Font and Typography Settings
**What it does:** The Super Admin configures the fonts and typography so the branded surfaces use the institute's typeface.

**Sub-features:**
- Font family: the primary and secondary font families
- Font weights: the font weights available
- Font sizes: the base font size and scale
- Line height: the line height for body text
- Typography preview: the preview of the typography on sample text
- Available on web
- Event logging (action performed)
- Audit logging of font and typography settings

**Super Admin User Journey:**
1. As a Super Admin, open the font and typography settings.
2. Set the font families, weights, and sizes.
3. Configure the line height.
4. Preview the typography on sample text.
5. Save and verify the typography is applied across the branded surfaces.

**Rules & Edge Cases:**
- A font family must be an allowed or uploaded font.
- A font weight must be available for the selected family.
- A font size scale is derived from the base size.
- A typography preview renders the settings on sample text.
- A typography change applies to all branded surfaces on the next load.
- A font not loaded falls back to the system default.
- Configuration changes are audit-logged with the actor and timestamp.

### 2.4 Asset Versioning and Preview
**What it does:** The Super Admin versions and previews branding assets so changes are tracked and reviewable before going live.

**Sub-features:**
- Asset versioning: the version history per asset
- Version restore: the restore of a previous asset version
- Asset preview: the preview of an asset in its branded context
- Version comparison: the comparison of two asset versions
- Version retention: the retention of historical versions
- Available on web
- Event logging (action performed)
- Audit logging of asset versioning and preview

**Super Admin User Journey:**
1. As a Super Admin, open the asset versioning view.
2. Review the version history per asset.
3. Preview an asset in its branded context.
4. Compare two versions and restore a previous version if needed.
5. Verify the retention of historical versions.

**Rules & Edge Cases:**
- An asset version is created on each replacement.
- A version restore sets the asset to the selected version.
- An asset preview shows the asset in its branded context.
- A version comparison shows the differences between two versions.
- A version beyond the retention count is pruned.
- A version restore is itself recorded as a new version.
- Versioning actions are audit-logged with the actor and timestamp.