Team → Single sign-on, for owners of an account on PingWise Business. Other accounts see a short note with a link to the plan. Sign-in goes through OpenID Connect; SAML is not supported.
In your identity provider
Create an OpenID Connect web application:
- Okta: Applications → Create App Integration → OIDC – Web Application.
- Microsoft Entra ID: App registrations → New registration, with a Web platform.
- Google Workspace: Google Cloud console → Credentials → OAuth client ID, type Web application.
- Auth0, JumpCloud, Keycloak and any other OpenID Connect provider work the same way.
Scopes: openid email profile. The redirect URI has the form https://app.pingwise.com/accounts/oidc/sso-<id>/login/callback/; the exact one is shown, with a copy button, on the Single sign-on page after you first save it.
In PingWise
- Issuer: the provider's https address, for example
https://<you>.okta.com,https://login.microsoftonline.com/<tenant id>/v2.0orhttps://accounts.google.com. We read its/.well-known/openid-configurationbefore saving. - Client ID and client secret: the secret is stored encrypted and shown only by its last four characters.
- Domains: which of the account's verified domains may use it; their subdomains are included.
- Role for new people: Member or Viewer.
- Button text: «Single sign-on» unless you change it.
- On / off, and Require it for members (see below).
Signing in
On the sign-in page, Company sign-in? Single sign-on asks for a work email and continues to your provider. The address must be on one of the selected domains; any other is refused. An existing PingWise login with that address is connected to it. Someone new gets a login with the address already confirmed and joins the account with the role you chose, at their first sign-in; no invitation is needed. PingWise uses the email and sub claims, and name, given_name and family_name for the name.
Requiring it
Require it for members can be turned on once at least one sign-in through the connection has worked. From then on, members and viewers with addresses on the selected domains cannot sign in with a password, an email link, Google, GitHub or Microsoft: they are sent to single sign-on. Owners are never held back, so a broken provider cannot lock the account.
People who leave
Someone removed at your provider can no longer sign in through it. Their membership in PingWise is not removed on its own, since there is no automatic provisioning: remove them under Team. A session they already have lasts until it ends or they sign out, and without Require it an email link to a mailbox they still read would still work.
Remove single sign-on deletes the connection; everyone signs in the usual ways again.
Last change: 7 November 2026.