# 6. Policies & Agreements User Type: **Super Administrator** Source: *Mi Digital Academy - Education CRM Features Document* --- ## 6. Policies & Agreements ### 6.1 Terms of Service **What it does:** Provides the terms of service: the terms (the terms, the clause, the date) are provided for the users, so the users are bound (the terms are the agreement). The Super Administrator provides the terms of service (the terms, the clause, the date) so the terms are structured and the agreement is explicit. **Sub-features:** - Terms: the terms (the terms, the clause, the date) - Clause: the clause (the clause of the terms, the text, the date) - Terms version: the version (the version of the terms, the number, the date) - Terms status: the status (the active, the archived) - Terms count: the count (the count of the clauses) - Terms view: the view (the terms, the clauses, the versions, the dates) - Terms export: the export (the terms, the format, the version) - Audit logging of the terms of service configuration **Super Administrator User Journey:** 1. Super Admin provides the terms of service: the terms (the terms, the clause, the date), the clause (the clause of the terms, the text, the date), and the version (the version of the terms, the number, the date); the terms are explicit. 2. Creates the clause: the clause (the clause of the terms, the text, the date); the clause is the rule. 3. Sets the terms version: the version (the version of the terms, the number, the date); the version is the iteration. 4. Views the terms status: the status (the active, the archived); the status is the state. 5. Views the terms count: the count (the count of the clauses); the count is the measure. 6. Exports the terms: the export (the terms, the format, the version); the export is the record. 7. The terms are provided: the terms, the clauses, the versions, the dates, so the agreement is complete. 8. The terms of service configuration is audit-logged with the terms, the version, and the timestamp. **Rules & Edge Cases:** - The terms are the agreement (the terms, the clause, the date); the terms are the contract. - The clause is the rule (the clause of the terms, the text, the date); the clause is the provision. - The terms version is the iteration (the version of the terms, the number, the date); the version is the revision. - The terms status is the state (the active, the archived); the status is the control. - The terms are provided (the terms, the clauses, the versions, the dates); the agreement is managed. - Terms of service configuration is audit-logged with the terms, version, and timestamp. ### 6.2 Privacy Policy **What it does:** Provides the privacy policy: the policy (the policy, the clause, the date) is provided for the users, so the privacy is defined (the policy is the commitment). The Super Administrator provides the privacy policy (the policy, the clause, the date) so the policy is structured and the commitment is explicit. **Sub-features:** - Policy: the policy (the policy, the clause, the date) - Clause: the clause (the clause of the policy, the text, the date) - Policy version: the version (the version of the policy, the number, the date) - Policy status: the status (the active, the archived) - Policy count: the count (the count of the clauses) - Policy view: the view (the policies, the clauses, the versions, the dates) - Policy export: the export (the policies, the format, the version) - Audit logging of the privacy policy configuration **Super Administrator User Journey:** 1. Super Admin provides the privacy policy: the policy (the policy, the clause, the date), the clause (the clause of the policy, the text, the date), and the version (the version of the policy, the number, the date); the policy is explicit. 2. Creates the clause: the clause (the clause of the policy, the text, the date); the clause is the rule. 3. Sets the policy version: the version (the version of the policy, the number, the date); the version is the iteration. 4. Views the policy status: the status (the active, the archived); the status is the state. 5. Views the policy count: the count (the count of the clauses); the count is the measure. 6. Exports the policies: the export (the policies, the format, the version); the export is the record. 7. The policy is provided: the policies, the clauses, the versions, the dates, so the commitment is complete. 8. The privacy policy configuration is audit-logged with the policy, the version, and the timestamp. **Rules & Edge Cases:** - The policy is the commitment (the policy, the clause, the date); the policy is the promise. - The clause is the rule (the clause of the policy, the text, the date); the clause is the provision. - The policy version is the iteration (the version of the policy, the number, the date); the version is the revision. - The policy status is the state (the active, the archived); the status is the control. - The policy is provided (the policies, the clauses, the versions, the dates); the commitment is managed. - Privacy policy configuration is audit-logged with the policy, version, and timestamp. ### 6.3 Refund Policy **What it does:** Provides the refund policy: the policy (the policy, the clause, the date) is provided for the refunds, so the refunds are defined (the policy is the rule). The Super Administrator provides the refund policy (the policy, the clause, the date) so the policy is structured and the rule is explicit. **Sub-features:** - Policy: the policy (the policy, the clause, the date) - Clause: the clause (the clause of the policy, the text, the date) - Policy version: the version (the version of the policy, the number, the date) - Policy status: the status (the active, the archived) - Policy count: the count (the count of the clauses) - Policy view: the view (the policies, the clauses, the versions, the dates) - Policy export: the export (the policies, the format, the version) - Audit logging of the refund policy configuration **Super Administrator User Journey:** 1. Super Admin provides the refund policy: the policy (the policy, the clause, the date), the clause (the clause of the policy, the text, the date), and the version (the version of the policy, the number, the date); the policy is explicit. 2. Creates the clause: the clause (the clause of the policy, the text, the date); the clause is the rule. 3. Sets the policy version: the version (the version of the policy, the number, the date); the version is the iteration. 4. Views the policy status: the status (the active, the archived); the status is the state. 5. Views the policy count: the count (the count of the clauses); the count is the measure. 6. Exports the policies: the export (the policies, the format, the version); the export is the record. 7. The policy is provided: the policies, the clauses, the versions, the dates, so the rule is complete. 8. The refund policy configuration is audit-logged with the policy, the version, and the timestamp. **Rules & Edge Cases:** - The policy is the rule (the policy, the clause, the date); the policy is the commitment. - The clause is the provision (the clause of the policy, the text, the date); the clause is the detail. - The policy version is the iteration (the version of the policy, the number, the date); the version is the revision. - The policy status is the state (the active, the archived); the status is the control. - The policy is provided (the policies, the clauses, the versions, the dates); the rule is managed. - Refund policy configuration is audit-logged with the policy, version, and timestamp. ### 6.4 Acceptable Use Policy **What it does:** Provides the acceptable use policy: the policy (the policy, the clause, the date) is provided for the usage, so the usage is defined (the policy is the boundary). The Super Administrator provides the acceptable use policy (the policy, the clause, the date) so the policy is structured and the boundary is explicit. **Sub-features:** - Policy: the policy (the policy, the clause, the date) - Clause: the clause (the clause of the policy, the text, the date) - Policy version: the version (the version of the policy, the number, the date) - Policy status: the status (the active, the archived) - Policy count: the count (the count of the clauses) - Policy view: the view (the policies, the clauses, the versions, the dates) - Policy export: the export (the policies, the format, the version) - Audit logging of the acceptable use policy configuration **Super Administrator User Journey:** 1. Super Admin provides the acceptable use policy: the policy (the policy, the clause, the date), the clause (the clause of the policy, the text, the date), and the version (the version of the policy, the number, the date); the policy is explicit. 2. Creates the clause: the clause (the clause of the policy, the text, the date); the clause is the rule. 3. Sets the policy version: the version (the version of the policy, the number, the date); the version is the iteration. 4. Views the policy status: the status (the active, the archived); the status is the state. 5. Views the policy count: the count (the count of the clauses); the count is the measure. 6. Exports the policies: the export (the policies, the format, the version); the export is the record. 7. The policy is provided: the policies, the clauses, the versions, the dates, so the boundary is complete. 8. The acceptable use policy configuration is audit-logged with the policy, the version, and the timestamp. **Rules & Edge Cases:** - The policy is the boundary (the policy, the clause, the date); the policy is the limit. - The clause is the rule (the clause of the policy, the text, the date); the clause is the provision. - The policy version is the iteration (the version of the policy, the number, the date); the version is the revision. - The policy status is the state (the active, the archived); the status is the control. - The policy is provided (the policies, the clauses, the versions, the dates); the boundary is managed. - Acceptable use policy configuration is audit-logged with the policy, version, and timestamp. ### 6.5 Cookie Policy **What it does:** Provides the cookie policy: the policy (the policy, the clause, the date) is provided for the cookies, so the cookies are defined (the policy is the disclosure). The Super Administrator provides the cookie policy (the policy, the clause, the date) so the policy is structured and the disclosure is explicit. **Sub-features:** - Policy: the policy (the policy, the clause, the date) - Clause: the clause (the clause of the policy, the text, the date) - Policy version: the version (the version of the policy, the number, the date) - Policy status: the status (the active, the archived) - Policy count: the count (the count of the clauses) - Policy view: the view (the policies, the clauses, the versions, the dates) - Policy export: the export (the policies, the format, the version) - Audit logging of the cookie policy configuration **Super Administrator User Journey:** 1. Super Admin provides the cookie policy: the policy (the policy, the clause, the date), the clause (the clause of the policy, the text, the date), and the version (the version of the policy, the number, the date); the policy is explicit. 2. Creates the clause: the clause (the clause of the policy, the text, the date); the clause is the rule. 3. Sets the policy version: the version (the version of the policy, the number, the date); the version is the iteration. 4. Views the policy status: the status (the active, the archived); the status is the state. 5. Views the policy count: the count (the count of the clauses); the count is the measure. 6. Exports the policies: the export (the policies, the format, the version); the export is the record. 7. The policy is provided: the policies, the clauses, the versions, the dates, so the disclosure is complete. 8. The cookie policy configuration is audit-logged with the policy, the version, and the timestamp. **Rules & Edge Cases:** - The policy is the disclosure (the policy, the clause, the date); the policy is the notice. - The clause is the rule (the clause of the policy, the text, the date); the clause is the provision. - The policy version is the iteration (the version of the policy, the number, the date); the version is the revision. - The policy status is the state (the active, the archived); the status is the control. - The policy is provided (the policies, the clauses, the versions, the dates); the disclosure is managed. - Cookie policy configuration is audit-logged with the policy, version, and timestamp. ### 6.6 Click-through Acceptance **What it does:** Provides the click-through acceptance: the acceptance of the policies (the acceptance, the user, the policy, the date) is done by the click, so the policies are accepted (the acceptance is the agreement). The Super Administrator provides the click-through acceptance (the acceptance, the user, the policy, the date) so the acceptance is structured and the agreement is explicit. **Sub-features:** - Acceptance: the acceptance (the acceptance, the user, the policy, the date) - User: the user (the user, the name, the acceptance) - Policy: the policy (the policy, the name, the date) - Acceptance status: the status (the accepted, the not-accepted) - Acceptance count: the count (the count of the acceptances) - Acceptance view: the view (the acceptances, the users, the policies, the dates) - Acceptance export: the export (the acceptances, the format, the policy) - Audit logging of the click-through acceptance **Super Administrator User Journey:** 1. Super Admin provides the click-through acceptance: the acceptance (the acceptance, the user, the policy, the date), the user (the user, the name, the acceptance), and the policy (the policy, the name, the date); the acceptance is explicit. 2. Selects the user: the user (the user, the name, the acceptance); the user is the acceptor. 3. Selects the policy: the policy (the policy, the name, the date); the policy is the document. 4. Views the acceptance status: the status (the accepted, the not-accepted); the status is the state. 5. Views the acceptance count: the count (the count of the acceptances); the count is the measure. 6. Exports the acceptances: the export (the acceptances, the format, the policy); the export is the record. 7. The policies are accepted: the acceptances, the users, the policies, the dates, so the agreement is complete. 8. The click-through acceptance is audit-logged with the acceptance, the user, and the timestamp. **Rules & Edge Cases:** - The acceptance is the agreement (the acceptance, the user, the policy, the date); the acceptance is the consent. - The user is the acceptor (the user, the name, the acceptance); the user is the party. - The policy is the document (the policy, the name, the date); the policy is the terms. - The acceptance status is the state (the accepted, the not-accepted); the status is the control. - The policies are accepted (the acceptances, the users, the policies, the dates); the agreement is managed. - Click-through acceptance is audit-logged with the acceptance, user, and timestamp. ### 6.7 Version Control for Policies **What it does:** Controls the versions of the policies: the version of the policy (the version, the policy, the change, the date) is controlled, so the policies are versioned (the version is the history). The Super Administrator controls the versions of the policies (the version, the policy, the change, the date) so the version is structured and the history is explicit. **Sub-features:** - Version: the version (the version, the policy, the change, the date) - Policy: the policy (the policy, the name, the date) - Version change: the change (the change of the version, the edit, the date) - Version number: the number (the number of the version, the sequence) - Version status: the status (the active, the archived) - Version count: the count (the count of the versions) - Version view: the view (the versions, the policies, the changes, the dates) - Audit logging of the policy version control **Super Administrator User Journey:** 1. Super Admin controls the version of the policy: the version (the version, the policy, the change, the date), the policy (the policy, the name, the date), and the change (the change of the version, the edit, the date); the version is explicit. 2. Selects the policy: the policy (the policy, the name, the date); the policy is the document. 3. Sets the version change: the change (the change of the version, the edit, the date); the change is the edit. 4. Sets the version number: the number (the number of the version, the sequence); the number is the sequence. 5. Views the version status: the status (the active, the archived); the status is the state. 6. Views the version count: the count (the count of the versions); the count is the measure. 7. The policies are versioned: the versions, the policies, the changes, the dates, so the history is complete. 8. The policy version control is audit-logged with the version, the policy, and the timestamp. **Rules & Edge Cases:** - The version is the history (the version, the policy, the change, the date); the version is the record. - The policy is the document (the policy, the name, the date); the policy is the terms. - The version change is the edit (the change of the version, the edit, the date); the change is the modification. - The version status is the state (the active, the archived); the status is the control. - The policies are versioned (the versions, the policies, the changes, the dates); the history is managed. - Policy version control is audit-logged with the version, policy, and timestamp. ### 6.8 Notification of Policy Changes **What it does:** Notifies the policy changes: the notification of the changes (the notification, the policy, the change, the date) is sent to the users, so the users are informed (the notification is the update). The Super Administrator notifies the policy changes (the notification, the policy, the change, the date) so the notification is structured and the update is explicit. **Sub-features:** - Notification: the notification (the notification, the policy, the change, the date) - Policy: the policy (the policy, the name, the date) - Change: the change (the change of the policy, the edit, the date) - Notification status: the status (the sent, the read, the acknowledged) - Notification count: the count (the count of the notifications) - Notification view: the view (the notifications, the policies, the changes, the dates) - Notification export: the export (the notifications, the format, the policy) - Audit logging of the policy change notification **Super Administrator User Journey:** 1. Super Admin notifies the policy change: the notification (the notification, the policy, the change, the date), the policy (the policy, the name, the date), and the change (the change of the policy, the edit, the date); the notification is explicit. 2. Selects the policy: the policy (the policy, the name, the date); the policy is the document. 3. Sets the change: the change (the change of the policy, the edit, the date); the change is the edit. 4. Views the notification status: the status (the sent, the read, the acknowledged); the status is the state. 5. Views the notification count: the count (the count of the notifications); the count is the measure. 6. Exports the notifications: the export (the notifications, the format, the policy); the export is the record. 7. The users are informed: the notifications, the policies, the changes, the dates, so the update is complete. 8. The policy change notification is audit-logged with the notification, the policy, and the timestamp. **Rules & Edge Cases:** - The notification is the update (the notification, the policy, the change, the date); the notification is the notice. - The policy is the document (the policy, the name, the date); the policy is the terms. - The change is the edit (the change of the policy, the edit, the date); the change is the modification. - The notification status is the state (the sent, the read, the acknowledged); the status is the control. - The users are informed (the notifications, the policies, the changes, the dates); the update is managed. - Policy change notification is audit-logged with the notification, policy, and timestamp.