SSO / SAML
Single sign-on lets your team access Pulse using your existing identity provider (IdP) — such as Okta, Azure AD/Entra, Google Workspace or any SAML 2.0 provider — instead of separate passwords.
Benefits
- Central control — deprovision a user in your IdP and their Pulse access ends.
- Stronger security — enforce MFA and your IdP's policies.
- Less friction — one login for your whole team.
Setup outline
- Console → Settings → SSO.
- Pulse shows the service-provider details (ACS URL and entity ID) at the reserved
samlroute. - In your IdP, create a SAML app using those details.
- Paste your IdP's metadata/certificate back into Pulse.
- Test with a single account before rolling out to everyone.
Important
Keep at least one password-based owner account until SSO is verified end-to-end, so a misconfiguration can't lock everyone out.
Note
SSO availability may depend on your plan. Check Settings → SSO for what's enabled on your organization.