Enterprise SSO
SAML 2.0 single sign-on. Self-serve in 10 minutes, on Pro and above.
Route your team through Okta, Microsoft Entra, Google Workspace, OneLogin, JumpCloud, or any SAML 2.0 identity provider. Paste three identifiers into your IdP, add one DNS TXT record, SSO is live. No custom integration. No implementation call.
In plain English: single sign-on (SSO) lets your team log in to NightMaven with the work account they already use, like Okta, Microsoft or Google. Your IT team controls who has access, and when someone leaves, their access ends in one place.
NightMaven supports SAML 2.0 single sign-on on the Pro, Business, and Business+ plans. Configure your identity provider — Okta, Microsoft Entra, Google Workspace, OneLogin, JumpCloud, or any SAML 2.0–compliant IdP — in about 10 minutes using a self-serve flow inside the admin panel. Domain ownership is verified via a DNS TXT record before SSO activates. Once active, every user on your verified domain routes through your IdP, with MFA delegated to your identity provider and every sign-in recorded in your workspace's audit log. JIT user provisioning is supported today. SCIM provisioning and IdP-initiated flow are on the roadmap — called out below.
How NightMaven SSO works
Three steps, each a few minutes:
- Paste three identifiers into your IdP. Create a SAML 2.0 application in Okta, Entra, or Google Workspace and paste NightMaven's ACS URL, Entity ID, and Metadata URL from
Settings → SSO. - Verify your domain with one DNS TXT record. NightMaven gives you the host and value; add it at Cloudflare, Route 53, GoDaddy, or wherever your DNS lives. Most registrars propagate in under a minute.
- That's it — SSO is enforced. Everyone on your verified domain routes through your IdP. Non-SSO sign-in paths (password, magic link, Google OAuth) are blocked at the API layer for users on that domain.
See the full 10-minute walkthrough for Okta, Entra, and Google Workspace — with screenshots, DNS examples, and rotation instructions.
SSO facts
- Plans
- Pro, Business, Business+
- Protocol
- SAML 2.0
- Flow
- SP-initiated (IdP-initiated on roadmap)
- Identity providers
- Okta, Microsoft Entra, Google Workspace, OneLogin, JumpCloud, any SAML 2.0 IdP
- NameID formats
- emailAddress, persistent
- User provisioning
- JIT on first sign-in (SCIM on roadmap)
- MFA
- Delegated to your IdP
- Domain verification
- DNS TXT record
- Setup time
- ~10 minutes, self-serve
- SAML validation
- Signature + freshness + replay protection enforced; unsigned assertions rejected
Security model
- Domain ownership is required. No one claims a domain they don't control — DNS TXT verification is mandatory before a domain activates. Without it, a malicious tenant could register
@google.comand hijack every Gmail user's login. - Domain exclusivity is enforced. A given email domain routes to one NightMaven workspace globally — not one per region, not one per plan, one period.
- SSO is enforced, not optional. Once a domain is verified and SSO is active, all non-SSO sign-in paths (password, magic link, Google OAuth) are blocked for users on that domain. Defense in depth at the API layer, not just the login UI.
- Service-role separation. NightMaven's API is the only process that holds admin credentials for your SSO provider. Your IdP secrets never touch browser code.
- Tamper-resistant audit log. Write-only from the application layer, with row-level security denying all external reads. The same RLS model governs every tenant in NightMaven — see our full security posture.
Your audit log
-
What's recorded, per event: actor (user ID + email), IP address, UTC timestamp, event type, target resource, and a structured JSON details payload. Applies to every SSO configuration change, every SSO sign-in (not just first login), MFA delegation, bypass attempts, forced sign-outs, and automatic 30-day downgrade cleanup.
-
Who uses it, and how: it's your workspace's audit log, not ours. Scoped to your tenant, write-only from the application layer, with row-level security denying all external reads. Accessible to workspace admins from the admin panel. Retained for the life of your subscription so your compliance team can reconstruct any session after the fact.
-
What this is not: not SOC 2 certified today. NightMaven is working toward SOC 2 Type I in 2026 and Type II after; the audit log's field coverage and tamper-resistance are designed to support that future audit, but the controls are documented-not-audited right now. If you need SOC 2 today, we're not your vendor. [src]
On the roadmap, said plainly
SCIM provisioning and deprovisioning
Not in the current release. JIT provisioning handles creation (a user signs in via SSO for the first time; NightMaven creates their profile and tenant membership). Deprovisioning is handled by deactivating the user in your IdP plus "Revoke all SSO sessions" in NightMaven when you need immediate session invalidation.
SCIM is a roadmap item. If your procurement requires SCIM push-provisioning today, we're not your vendor yet — let us know and we can tell you when we expect to ship it.
IdP-initiated SSO
SP-initiated only in the current release. Users start from app.wengrow.app/login rather than from an Okta dashboard tile. IdP-initiated flow is on the roadmap.
SSO FAQ
- Pro, Business, and Business+. SSO becomes available automatically within a minute of your subscription activating — no manual flag to flip.
- Yes — all three, plus OneLogin, JumpCloud, and any SAML 2.0–compliant identity provider. The setup guide has per-IdP walkthroughs with screenshots for Okta, Entra, and Google Workspace.
- Your IdP owns MFA. If you require TOTP, hardware key, or push-notification MFA in Okta / Entra / Google, your team sees those prompts when they sign in to NightMaven. Every SSO sign-in is logged with an sso.login_mfa_delegated audit event.
- No. Once a domain is SSO-enforced, every user on that domain must sign in via SSO — password, magic link, and Google OAuth are blocked at the API layer. Users on a different non-enforced domain (e.g. contractors on a personal email) can still use password / Google / magic-link sign-in normally.
- emailAddress (preferred) and persistent. Most IdPs default to one of these.
- Not today. NightMaven does JIT provisioning — users are auto-created on their first SSO sign-in. Deprovisioning is handled by deactivating the user in your IdP, plus a 'Revoke all SSO sessions' button in NightMaven for immediate session invalidation. SCIM is on the roadmap.
- SP-initiated only in the current release (users start from app.wengrow.app/login). IdP-initiated flow is on the roadmap.
- Signature validation is enforced. Response freshness (InResponseTo + NotOnOrAfter) is validated. Replay protection is enforced. Unsigned assertions are rejected.
- From the admin panel — workspace admins can filter by event type (e.g. sso.*) and export to CSV or JSON. If you need periodic push into your SIEM (Splunk, Datadog, etc.), that's available on enterprise contracts; contact us.
- NightMaven keeps your SSO configuration for 30 days. New SSO sign-ins are blocked immediately; existing sessions remain valid until they expire naturally; if you re-upgrade within 30 days your configuration is restored instantly. After 30 days the SSO provider is permanently deleted.
- NightMaven fetches IdP metadata from our backend — the public NightMaven egress IPs are published on our trust page. Allowlist those in your IdP's metadata endpoint restrictions.
Procurement
More questions from your security team?
We can walk your IT lead through our SAML validation policy — signature enforced, freshness (InResponseTo / NotOnOrAfter) checked, replay protected, unsigned assertions rejected — and answer your security questionnaire directly. Pro starts at $1,499/mo, with SSO included. See how we protect your data.
SSO in 10 minutes. No sales call required.
Self-serve setup, DNS-verified domain, audit-logged sign-ins. Included on every Pro plan.