Hourglass Content Intelligence
← All conversations

Conversation

20 Oct 2026, 01:15 UTC · 1 question · ID 03dde10fc13e
Who asked
Profile
We don’t have a profile for this visitor.
Question 1

“Can we force everyone to sign in with SSO?”

Answer
Partly answered

The /security page says users can sign in through an identity provider with enforced two-step login. It never says whether single sign-on can be made the only sign-in method for a workspace, or how admins regain access if the identity provider is down.

Section on the siteStatusTicket
/securitySingle sign-on (card)Partly answers it
Add SSO enforcement detail to the Single sign-on card on /security

Ticket

Paste this into your ticketing tool.

Add SSO enforcement detail to the Single sign-on card on /security

Who needs it: IT admins and security reviewers checking a vendor
Section: /security › Single sign-on (card)

What is missing:
- Whether admins can require single sign-on as the only way to sign in is not stated.
- What happens when the identity provider is unavailable, such as an admin recovery path, is not covered.
- Which plans include single sign-on enforcement is not stated.

Where: Update this section: Extend the "Single sign-on" card in "Security and control, built into every hub", beside "Field-level permissions" and "Audit history".

What to do:
1. Confirm with the security team and product whether single sign-on can be enforced for every user, what recovery path exists if the identity provider is down, and which plans include it.
2. Add the confirmed enforcement option and recovery path to the Single sign-on card.
3. Link the card to setup guidance once it exists, and note the plan that includes it.

Done when: The Single sign-on card on /security states whether SSO can be required for all users, how access is recovered if the identity provider is down, and which plans include it.

From: conversation 03dde10fc13e, question 1: "Can we force everyone to sign in with SSO?"
Who needs it: IT admins and security reviewers checking a vendor
What is missing
  • Whether admins can require single sign-on as the only way to sign in is not stated.
  • What happens when the identity provider is unavailable, such as an admin recovery path, is not covered.
  • Which plans include single sign-on enforcement is not stated.
Where
Update this section: Extend the "Single sign-on" card in "Security and control, built into every hub", beside "Field-level permissions" and "Audit history".
What to do
  1. Confirm with the security team and product whether single sign-on can be enforced for every user, what recovery path exists if the identity provider is down, and which plans include it.
  2. Add the confirmed enforcement option and recovery path to the Single sign-on card.
  3. Link the card to setup guidance once it exists, and note the plan that includes it.
Done when: The Single sign-on card on /security states whether SSO can be required for all users, how access is recovered if the identity provider is down, and which plans include it.
Answer full page
Yes. You can make SSO the only way to sign in to your workspace, with a recovery path in case your identity provider is down. The docs below walk through the setup.
Sections in the answer pageStatus
/securitySingle sign-on (card)Partly answers it

Questions and answers are shown as recorded. Status, what is missing and what to do are our analysis of the live site, read 22 Oct 2026.