Supported protocols
SAML 2.0
HTTP Redirect binding (SP → IdP) and HTTP POST binding (IdP → SP)
OpenID Connect
Requires Issuer URL and Client ID. Client Secret is optional.
Azure AD
Requires Azure AD Domain, Client ID, and Client Secret.
Supported identity providers
- Okta
- Azure Active Directory
- Google Workspace
- Ping Identity
- Auth0
- Custom SAML providers
Benefits
Centralized Identity
Manage all Dashboard access through your existing identity provider.
Auto-Deprovisioning
When a user’s account is deactivated at the IdP, they immediately lose Dashboard access.
MFA Enforcement
Enforce multi-factor authentication and conditional access policies at the IdP level.
Audit Logging
Comprehensive audit trail of all SSO authentication events for compliance.
Set up SSO
Request SSO enablement
Contact your Technical Account Manager (TAM) to request SSO setup for your organization.
Configure your identity provider
Truv generates a secure self-service configuration link for your IT team to set up the connection in your IdP.
Notify Truv
Let your TAM know when the IdP configuration is complete so Truv can validate the connection.
Once SSO is activated, all team members authenticate through your IdP. Any MFA or conditional access policies you’ve configured apply automatically.
User experience
After SSO is enabled:- Users navigate to the Dashboard login page
- They enter their work email address
- They’re redirected to your identity provider for authentication
- After successful authentication, they’re returned to the Dashboard with full access based on their assigned role
Next steps
Security & Compliance
Data protection, encryption, and compliance certifications
Dashboard
Navigate the Dashboard interface
Authentication
API credentials and access management