Insight

Please include "Referred to HR" as any employee disciplinary action must be confidential. There are several team members who could see the actions taken and would be a violation of the employee's rights.

Providing API access to read and write app, approval, and licensing data would allow districts to better integrate the platform with existing tools and workflows. Programmatic access to statuses and metadata would reduce the need to bounce between systems and enable automation with tools such as helpdesk platforms or internal systems. Being able to build integrations on top of the platform would give districts greater flexibility and control while improving efficiency and data consistency across tools.

The platform should allow a single license to be associated with multiple apps. In practice, many purchases cover multiple products under one invoice or PO, and it can be difficult or artificial to split those into separate licenses within the system. This is true both for bundled paid products and for free tools that effectively share a single “license” state. Requiring separate licenses for each app leads to duplicate data entry, increases the risk of inconsistencies, and does not accurately reflect how licensing is managed in the real world. Supporting one-to-many license associations would simplify workflows and improve data accuracy.

When viewing an app from Application Activity, the “Application Profile” page does not provide an easy way to switch to that app’s Approval Management or Licensing views and visa versa. Users must navigate to a different area of the platform and re-search for the same app, which is inefficient. Since app details, approval status, and licensing information are closely related, it should be easy to move between them directly from the app profile. This could be accomplished by making the existing “Approved” and “Licensed” indicators clickable links, or by introducing tabs that allow users to switch between app info, approval, and licensing properties for the same app.

Having two separate expiration dates - one on the license and another on the app approval page - is confusing for users. While I understand these could represent different concepts (such as a license renewal versus a periodic approval review), that distinction is not clear in the UI. If the intent is an approval review cycle, the field should be clearly labeled as something like a Review Date or Approval Review Date rather than an expiration. Otherwise, the license expiration/renewal date should automatically populate the app expiration date. Requiring staff to enter the same information in multiple places increases the risk of inconsistent data, errors, and confusion when viewing or managing app status.

The App Library is currently accessed via the book icon in the top-right, which is easy to miss and confusing for users. Since the App Library is a core part of managing apps, it would be more intuitive for it to live under App Management, with the Public List link presented as a sub-menu item under Public List Management rather than being hidden behind the book icon. From my experience onboarding staff, overall navigation between several areas of the platform is not intuitive, and clearer, more predictable placement of key links would significantly improve usability for new and infrequent users.

Would like to ability to connect teacher app requests that come through Digital Insight directly to our preferred IT Ticket Portal

It would be great if DI could pull the list of apps that we have already approved for SSO sign-ins and mark them as approved already.

I currently use our helpdesk to manage all requests for apps/sites/etc. I cannot see pulling my staff to another portal for web/app requests. Tying Digital Insight to our helpdesk would allow us to create workflows that auto build and populate the approved/denied lists. Currently we have a spreadsheet I want to light on fire, but we can update it with a ticket automagically. I want to utilize the app library with teachers so they have a place to look for ideas. Sort of a way to see what others are using.

Districts would like the ability to have apps that correlate to whole URLS. Currently if the client is using something like Pearson, even though there are multiple product they could be using, we only categorize the app in the library and track data based on the host URL and not the whole URL. It would be great to add this ability so district can track the product interactions.