# 4. Data Portability

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

---

## 4. Data Portability

### 4.1 User Data Portability (User-Initiated Export)
**What it does:** Provides the user data portability: the portability of the user data (the portability, the user, the data, the date) is provided by the user's request, so the user can take the data (the portability is the freedom). The Super Administrator provides the user data portability (the portability, the user, the data, the date) so the portability is structured and the freedom is explicit.

**Sub-features:**
- Portability: the portability (the portability, the user, the data, the date)
- User: the user (the user, the name, the portability)
- Data: the data (the data of the user, the type, the date)
- Request: the request (the request of the user, the date)
- Portability status: the status (the completed, the in-progress, the failed)
- Portability count: the count (the count of the portabilities)
- Portability view: the view (the portabilities, the users, the data, the dates)
- Audit logging of the user data portability

**Super Administrator User Journey:**
1. Super Admin provides the user data portability: the portability (the portability, the user, the data, the date), the user (the user, the name, the portability), and the data (the data of the user, the type, the date); the portability is explicit.
2. Selects the user: the user (the user, the name, the portability); the user is the owner.
3. Selects the data: the data (the data of the user, the type, the date); the data is the personal data.
4. Receives the request: the request (the request of the user, the date); the request is the trigger.
5. Views the portability status: the status (the completed, the in-progress, the failed); the status is the state.
6. Views the portability count: the count (the count of the portabilities); the count is the measure.
7. The user can take the data: the portabilities, the users, the data, the dates, so the freedom is complete.
8. The user data portability is audit-logged with the portability, the user, and the timestamp.

**Rules & Edge Cases:**
- The portability is the freedom (the portability, the user, the data, the date); the portability is the right.
- The user is the owner (the user, the name, the portability); the user is the subject.
- The data is the personal data (the data of the user, the type, the date); the data is the content.
- The portability status is the state (the completed, the in-progress, the failed); the status is the control.
- The user can take the data (the portabilities, the users, the data, the dates); the freedom is managed.
- User data portability is audit-logged with the portability, user, and timestamp.

### 4.2 Bulk Data Export for Compliance
**What it does:** Provides the bulk data export for compliance: the export of the data (the export, the scope, the data, the date) is done in bulk for the compliance, so the compliance is supported (the export is the transfer). The Super Administrator provides the bulk data export for compliance (the export, the scope, the data, the date) so the export is structured and the transfer is explicit.

**Sub-features:**
- Export: the export (the export, the scope, the data, the date)
- Scope: the scope (the scope of the export, the data, the date)
- Data: the data (the data of the export, the type, the date)
- Compliance: the compliance (the compliance, the regulation, the date)
- Export status: the status (the completed, the in-progress, the failed)
- Export count: the count (the count of the exports)
- Export view: the view (the exports, the scopes, the data, the dates)
- Audit logging of the bulk data export

**Super Administrator User Journey:**
1. Super Admin provides the bulk data export for compliance: the export (the export, the scope, the data, the date), the scope (the scope of the export, the data, the date), and the data (the data of the export, the type, the date); the export is explicit.
2. Sets the scope: the scope (the scope of the export, the data, the date); the scope is the boundary.
3. Selects the data: the data (the data of the export, the type, the date); the data is the content.
4. Selects the compliance: the compliance (the compliance, the regulation, the date); the compliance is the requirement.
5. Views the export status: the status (the completed, the in-progress, the failed); the status is the state.
6. Views the export count: the count (the count of the exports); the count is the measure.
7. The compliance is supported: the exports, the scopes, the data, the dates, so the transfer is complete.
8. The bulk data export is audit-logged with the export, the scope, and the timestamp.

**Rules & Edge Cases:**
- The export is the transfer (the export, the scope, the data, the date); the export is the move.
- The scope is the boundary (the scope of the export, the data, the date); the scope is the limit.
- The data is the content (the data of the export, the type, the date); the data is the payload.
- The compliance is the requirement (the compliance, the regulation, the date); the compliance is the obligation.
- The compliance is supported (the exports, the scopes, the data, the dates); the transfer is managed.
- Bulk data export is audit-logged with the export, scope, and timestamp.