Navigating the Apps Section on StudentDPA for Vendors
The Apps section on StudentDPA offers a suite of pages designed to help vendors manage their apps, ensuring accurate representation and compliance with legal requirements. Here's a breakdown of each page and how to utilize them:
Profile Page
Update App Information: Vendors can edit the app's URL and provide a detailed description. This information will populate the app's profile page, serving as an introduction to LEAs and educators.
- Content Areas: Select checkboxes corresponding to the app's relevant content areas (e.g., Health, Math, Social Science, English Language Arts). This categorization helps LEAs and teachers find apps suited to specific educational content.
- Grade Levels: Indicate the app's target grade levels, from TK (Transitional Kindergarten) through 12th grade, enabling precise alignment with educational needs.
Legal Info Page
Essential Legal Details: Input critical information like App Name, Vendor Name, and address. These details are incorporated into the DPA.
Designated Legal Representative: Specify the main contact for DPAs, including name, title, email, and phone. This person will be the primary point of contact for legal matters related to the app.
LEA Contracts Page
View LEA Agreements: This section lists LEAs that have countersigned DPAs with your app, presented in a table format showing the LEA, Region, Start and End dates, and an Action column for managing agreements.
Managers Page
Manage App Oversight: Similar to adding Vendor Managers, App Managers can be assigned for specific apps, allowing for focused management. This is particularly useful for larger companies with a diverse app portfolio.
- Roles for App Managers: Assign roles such as Edit Info, View Contracts, Sign Agreements, and Email Signed Contracts, tailoring access to the needs of each manager.
Agreements Page
DPAs and Signatures: This section displays requests for DPAs to be signed and those already executed by the vendor. Each DPA is specific to a region, ensuring compliance across different states.
- Data Collected: Vendors indicate what data elements the app collects, using a detailed table with checkboxes for standard data types and fields for special circumstances.
- Security: Outline the security frameworks implemented by the app. A concise table allows vendors to check off applied security measures.
- Documents: Review and approve individual elements composing the DPA, including the National Agreement, General Offer Addendum, State-specific Addendum, data elements, and security frameworks.
This guide aims to provide vendors with a clear understanding of how to effectively manage their apps on StudentDPA, from updating app details and legal information to managing contracts and ensuring compliance with DPAs. Additional detailed tasks related to the review and approval of DPAs and specific management actions will be covered as needed.