All your companies, all your apps, one identity.
Your employees access all enterprise apps with one account and one sign-in. Identity is managed from one place, and access is revoked from one place.
In a holding structure, every app keeps its own user list.
That means ten separate accounts for every new hire, and ten separate accesses waiting to be closed for every leaver.
- A separate account and password for each app
- Forgotten passwords come back to IT as reset requests
- Leavers' access waits to be closed one by one
- Sign in once a day, move between apps without passwords
- IT's password reset workload drops
- All of a leaver's access closes in one action
An employee's journey in the organization is tracked with a single identity.
No forgotten accounts, no access left open, no overlooked permissions. The security gap organizations face most often disappears through the normal workings of the system.
| App | Onboarding | Company change | Leaving |
|---|---|---|---|
| Xtranet | on | on | off |
| HR portal | on | on | off |
| Accounting (Company A) | on | off | off |
| Accounting (Company B) | off | on | off |
This is a fictional example; company and app names are illustrative.
The answer to "what can this person access?" on a single screen.
Holding, company, department, role: who can access what is defined in one place. When an app is opened to a company newly joining the holding, there is no need to define users one by one.
You decide where additional verification is required.
For critical apps, a second verification layer is added on top of the password. MFA is mandatory when signing in to the accounting system, but not for the lunch menu.
Connects to your existing directories and speaks the industry's common language.
Wherever user data already lives remains the source; no one defines the same employee twice. Organizational changes flow into the identity system automatically.
Every app that speaks these standards, both the ones you use today and the ones you will buy tomorrow, connects to Vanta SSO. Your identity infrastructure is not locked into a single vendor's closed world.
Whether you have 500 employees or 50,000, the infrastructure is the same.
Cloud identity services charge a monthly fee per user; at holding scale that is a bill that grows every year. With Vanta SSO the infrastructure is yours and is not priced by user count.
Identity data is an organization's most sensitive data.
If you wish, Vanta SSO runs entirely on your own servers.
If you prefer a cloud deployment, it is ready to run on these platforms.
Common questions about Vanta SSO
Yes. Vanta SSO works in sync with your Active Directory and LDAP directories and integrates with your HR system. The source of user data does not change.
Any app that supports the OpenID Connect and OAuth 2.0 standards can be connected. [Approach for legacy apps that don't support these standards · to be confirmed]
Yes, it can run entirely on your own servers; your user data never leaves your organization. If you prefer the cloud, it is deployed on Azure, AWS or DigitalOcean.
There are no per-user fees. [License / project-based pricing model · to be confirmed]
[Gradual connection of apps and migration of users · to be confirmed]