Districts buy a lot of apps. Some get used every day. Others quietly gather dust after the first semester. The problem is that most IT teams don't find out which is which until renewal season, by which point it's too late to make a good decision. That's the gap RapidIdentity Insights is built to close.
What Insights actually shows you
Insights is the analytics engine built into RapidIdentity. It doesn't just tell you an app is licensed. It shows you how students and teachers are actually using it, down to the individual login. That includes:
- A full inventory of your SSO applications, including their status, security controls, and who has access to what
- Usage stats by user type, school, grade level, or location, so you can see exactly which apps are catching on and where
- Trend analysis and forecasting, so growth or decline in adoption shows up before it becomes a budget surprise
- Individual application launch events, if you need to drill down that far
- Engagement tracking, including which users haven't logged in today, this week, this month, or at all
- Authentication detail, down to the policy and method used for each login attempt, successful or not (coming soon)
Instead of guessing from anecdotes or a handful of teacher emails, you get a real picture of how your entire app ecosystem is used.
Why this matters for IT and curriculum teams
For IT, this is a straightforward way to cut costs and risk. An app nobody's logging into is wasted budget and an unmonitored access point. Insights gives you the data to make the case for consolidating or cutting tools, backed by numbers instead of opinions, and it flags account provisioning issues (like accounts that should have been deactivated but weren't) before they turn into bigger problems.
For curriculum and instructional teams, the same data works in reverse. If a tool the district invested in isn't catching on in a particular school or grade level, that's worth knowing early. Maybe it needs more training, maybe the rollout needs adjusting, or maybe it's just not the right fit. Either way, Insights turns "we think teachers like this" into "here's what's actually happening classroom by classroom."
Getting started
A few ways districts typically put Insights to work:
- Run an adoption audit before renewals. Pull usage and trend data a month or two before your renewal cycle, so you're negotiating from evidence, not habit.
- Compare adoption across schools or grade levels. If one school is getting strong usage out of an app and another isn't, that's worth investigating, not just noting.
- Watch engagement, not just app usage. Users who haven't authenticated in a while are often the first sign of an onboarding gap or a tool that's lost momentum.
- Share findings with curriculum leads. Usage data works best as a shared conversation between IT and instructional staff, not a report that stays in the IT department.
The goal isn't to police what teachers use. It's to give districts a clearer, evidence-based view of their own EdTech stack, making it easier to decide what to keep, retire, or invest more in with confidence.
Have you used Insights to clean up your app stack? Curious to hear what patterns other districts have found