Scaling behavioral health nationwide with centralized identity and full-stack visibility

Okta gave us the foundation. Stitchflow gave us visibility into everything else, the long tail of apps, the orphaned accounts, and the weird mismatches. It’s how we catch what we’d otherwise miss.

Dean Hoffman
Senior IT Manager, Rula
Rula’s challenge: Blind spots in offboarding across disconnected apps
Rula (formerly Path Mental Health) scaled its nationwide behavioral health network to 15,000+ licensed providers by 2025, supported by a hybrid workforce and a contractor-heavy care model. The IT team managed 1,200+ internal users and 140+ SaaS tools, many of which operated outside identity automation.
While Okta served as the identity backbone, offering MFA and SCIM provisioning for core apps, it couldn’t cover the long tail of non-SCIM, non-SSO tools used by contractors and fringe teams. Apps like Linear, Loom, Calendly, and Adobe either lacked automation support or required costly upgrades.
Contractor churn, shared logins, and siloed systems made it impossible to track access centrally. Offboarding became manual, audits were painful, and license sprawl was growing fast.
Core Challenges:
- Manual offboarding for dozens of disconnected apps
- Orphaned accounts lingering post-Okta deactivation
- Siloed or missing access evidence across non-SCIM tools
- Time-consuming audits and access reviews
- No centralized visibility across all users, apps, and licenses
“We were relying on spreadsheets and emails to plug gaps our IDP couldn’t reach.
It wasn’t sustainable, and we still couldn’t prove everything was covered”
— Dean Hoffman, Senior IT Manager, Rula
Stitchflow’s response: Centralized visibility and control across 100% of apps
Rula deployed Stitchflow alongside Okta to go beyond identity and deliver full-stack visibility not just into what’s managed, but also into what’s missed. Okta anchored identity. Stitchflow extended the visibility.
In under 30 minutes, Stitchflow connected to Rula’s Okta instance, pulled data from 140+ apps via API and CSV, and built a real-time graph of every user, every account, and every license, whether automated or not.
What Stitchflow enabled:
- Centralized visibility across all apps, not just Okta-managed
- Real-time detection of orphaned, mismatched, and hidden accounts
- Identification of pre-Okta remnants and overlooked users
- Slack-based workflows for fast access reviews
- Renewal audits across 140+ apps in minutes, not weeks
- No need to upgrade to premium SSO/SCIM plans
This wasn’t just another automation script. Stitchflow became Rula’s SaaS management layer, bridging
the identity gap and enforcing access governance even in disconnected, high-churn environments.
across all apps, Okta-managed and fringe tools alike
in offboarding processes
from manual SaaS access audits and reviews
with access tracking across SCIM and non-SCIM apps
across the contractor-heavy, long-tail app environment
The outcome
With Okta anchoring identity and Stitchflow extending coverage, Rula now runs a nationwide behavioral health network with centralized control over its full SaaS stack.
Access gaps don’t pile up. Audits don’t require fire drills. And IT no longer needs to choose between oversight and overhead.
Stitchflow complements Okta by handling apps outside its perimeter without added complexity, cost, or manual overhead.