As monday.com scaled, hundreds of business-critical apps that don't support SCIM or security APIs fell outside its existing identity tools. With thousands of employees relying on those apps, the gaps were hard to manage at scale, and manual access work raised risk and slowed IT down.
How did app growth outpace monday.com's identity tools?
Identity automation only reaches apps that support SSO and SCIM. As monday.com adopted more apps faster than those protocols could cover, a growing share of applications had to be managed by hand, which meant slower onboarding and offboarding, inconsistent access policies, and more room for error.
What did monday.com do about disconnected apps?
monday.com used Cerby to bring those apps under the same identity controls as the rest of the stack, automating access and credential management for apps with no SSO, SCIM, or API. That let the team apply consistent policies and lifecycle automation across every app, not just the connected ones.
What results did monday.com see?
- Secured more than 200 applications that fell outside traditional identity coverage
- Raised consistent access and credential coverage from 20% to 78% across applications
- Saved 3,300 IT hours a year by reducing manual identity lifecycle work
How does this fit with an existing identity stack?
Cerby completes the identity stack rather than replacing it. monday.com kept its existing tools as the system of record and extended their reach to the disconnected apps they couldn't connect to, so the same policies applied everywhere.
What you'll learn in this session
- How monday.com secured more than 200 applications outside traditional identity coverage
- How the team raised access and credential coverage from 20% to 78%
- How monday.com cut the cost and effort of identity lifecycle management, saving 3,300 IT hours a year
Presenters
Lior Zagury, Director of Global IT, monday.com
Matt Chiodi, Chief Strategy Officer, Cerby
