Skip to content
HookWatch beta
FeaturesUse casesPricingQuickstartSecurityCompare
Resources
Resources overviewGuidesIntegrationsComparisonsChangelogDocumentationMCP server
Sign in Start beta
Changelog v1.18.0 New Security

Workspace SSO and inactivity timeout

Single sign-on through your own SAML 2.0 or OIDC identity provider, with an optional Require SSO enforcement and a session inactivity timeout.

Published 1 min read
On this page

Larger teams want sign-in to run through their own identity provider. This release adds workspace single sign-on and tightens idle sessions.

Added

  • Workspace SSO — connect one external identity provider per workspace, over SAML 2.0 or OIDC, configured in Settings under Security. Members are matched to the provider at sign-in by their email domain.
  • Require SSO — a workspace can require SSO, at which point any member whose last sign-in was not through the identity provider is signed out. Platform admins are exempt so the operator console cannot lock itself out.
  • Inactivity timeout — sessions expire after a period of inactivity, so an unattended dashboard does not stay signed in indefinitely.

Notes

Release date comes from the v1.18.0 git tag (22 July 2026). An SSO identity is kept separate from an existing password account rather than silently linked; see the security overview.

Related resources

Changelog v1.17.0 MCP server and HTTP API docs The whole workspace API is exposed as roughly 48 MCP tools for AI assistants, alongside new public documentation for the HTTP API and MCP. 1 min read Changelog v1.19.0 Overage pricing on metered usage Paid plans can now run past their included usage with metered overage, with projected charges surfaced in billing settings before they land. 1 min read Changelog v1.14.0 Usage metering, pay-as-you-go, and entitlements Per-unit usage metering on an idempotent ledger, pay-as-you-go and subscription billing with overage and spending limits, and a general entitlements layer. 2 min read
Get started

See what happened to every webhook.

HookWatch keeps the request, the response, and every attempt for each delivery — so the debugging, retry, and replay steps in this article are a matter of reading, not reconstructing.

Start using HookWatch Read the documentation