Platform, Security & Integrations / Integrations

Single Sign-On (SSO)

Single Sign-On (SSO — see Glossary) lets employees log into the phone system’s admin portal and apps using the same company credentials they already use for email and other business tools, instead of remembering yet another separate username and password.

What’s the business benefit, beyond convenience?

Two things IT teams care about: fewer forgotten-password support tickets, and tighter security — when an employee leaves the company and their main company account is disabled, their phone-system access is cut off automatically along with it, instead of being a separate step someone has to remember.

Which identity systems does this work with?

Standard identity providers are supported, including Microsoft Azure AD (Entra ID) and other systems that speak the OAuth 2.0 standard (a widely used method that lets apps securely verify who you are without handling your password directly — see Glossary). If your business already uses a company-wide login system, it’s very likely compatible.

Does this apply to every login, or just the admin portal?

Single Sign-On can cover the web admin portal, the softphone and mobile apps, and any connected management tools — anywhere an employee would otherwise need a separate phone-system password.

Can we still require a second layer of security on top of SSO?

Yes — Two-Factor Authentication can be layered in through your identity provider, so logins require both a valid company account and a second verification step.

What does setup actually involve?

Connecting SSO is a one-time configuration between your identity provider and the phone system’s admin portal, typically handled during onboarding. Once connected, no per-employee setup is needed — access follows however your directory is already organized. See Directory Sync for how accounts themselves stay in sync.