🚀 Getting Started
Enterprise SSO — Connect Your Company Login
Enable Okta, Azure AD, or Google Workspace sign-in for your workspace. Self-serve setup on Enterprise — no support ticket required.
Sign in required
This guide covers in-app features. Sign in or create an account to follow along in your workspace.
Updated July 2, 2026
6 min read
Enterprise workspaces can require employees to sign in with your corporate identity provider (IdP). FuseIQ enterprise SSO uses industry-standard SAML/OIDC — the same approach trusted by regulated SaaS vendors — so IT keeps control of passwords, MFA, and offboarding.
Why teams enable SSO
- One login — staff use Okta, Azure AD, or Google Workspace instead of another password
- IT control — disable access in your IdP and FuseIQ access stops on next sign-in
- Faster procurement — security reviewers see SSO, audit logs, and our compliance pack in one place
- Flexible rollout — SSO members use corporate login; contractors can still use email or Google/GitHub if you allow it
What you need (IT admin)
1
An Enterprise FuseIQ workspace (upgrade on Billing).
2
Admin access to your IdP (Okta, Azure AD, Google Workspace, or any SAML/OIDC provider).
3
An SSO Connection ID (conn_...) after linking your IdP (your IT team creates this when connecting your identity provider to FuseIQ).
Enable SSO in FuseIQ
1
Sign in as workspace Owner → Settings → SSO.
2
Paste your SSO Connection ID (conn_...) and save.
3
Share your workspace SSO link with employees (shown on the SSO panel after save).
4
Test with one pilot user before mandating SSO org-wide.
💡
Email and social login still work for members not routed through SSO. You can roll out corporate login team by team.
⚠️
SSO requires a plan with SSO enabled (Pro+ / Enterprise per your pricing). Security reviewers can download controls at fuseiq.io/trust/compliance. SOC 2 Type II: request current status letter from FuseIQ security — do not assume a finished report without confirmation.
SIEM audit export (Team Plus+)
Pull machine-readable audit events for Splunk, Elastic, Datadog, or a SIEM collector:
GET /api/audit/siem?format=ndjson&limit=5000&since=2026-01-01T00:00:00Z Authorization: Bearer <session or API token>
Events include trace_id, actor, action, target, and compliance.siem_ready. Metering ops webhooks: set METERING_ALERT_WEBHOOK_URL.
Was this helpful?