Hourglass Content Intelligence
← All conversations

Conversation

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

“SSO sign-in fails and says the assertion expired. What's wrong?”

Answer
Not answered

The site only says Hourglass supports single sign-on through your identity provider with enforced two-step login. It has no SSO setup or troubleshooting guidance, nothing on sign-in errors such as an expired assertion, and no link to documentation.

Section on the siteStatusTicket
/resourcesGuides to get you startedMissing here
Add a single sign-on troubleshooting guide to /resources

Ticket

Paste this into your ticketing tool.

Add a single sign-on troubleshooting guide to /resources

Who needs it: IT admins managing single sign-on
Section: /resources › Guides to get you started

What is missing:
- No guide covers setting up or troubleshooting single sign-on.
- Common SSO sign-in errors, including an expired assertion, are not explained with their causes and fixes.
- No link to technical documentation for identity provider setup.

Where: Update this section: add a fifth card beside "Your first day", "Moving from your current CRM", "How agents work in Hourglass" and "Security and control".
  Related sections: Security and control · Single sign-on

What to do:
1. Confirm with engineering the common SSO sign-in errors, including expired assertions, their causes and the checks admins should run.
2. Write a guide card that lists the setup steps and the error checks, and links to the full documentation.
3. Point the Get help card "Talk to our team" to support for errors the guide doesn't resolve.

Done when: /resources has a single sign-on guide that explains the expired-assertion error and what to check.

From: conversation 150d8bc87ad3, question 1: "SSO sign-in fails and says the assertion expired. What's wrong?"
Who needs it: IT admins managing single sign-on
What is missing
  • No guide covers setting up or troubleshooting single sign-on.
  • Common SSO sign-in errors, including an expired assertion, are not explained with their causes and fixes.
  • No link to technical documentation for identity provider setup.
Where
Update this section: add a fifth card beside "Your first day", "Moving from your current CRM", "How agents work in Hourglass" and "Security and control".
Related sections
Security and control · Single sign-on
What to do
  1. Confirm with engineering the common SSO sign-in errors, including expired assertions, their causes and the checks admins should run.
  2. Write a guide card that lists the setup steps and the error checks, and links to the full documentation.
  3. Point the Get help card "Talk to our team" to support for errors the guide doesn't resolve.
Done when: /resources has a single sign-on guide that explains the expired-assertion error and what to check.
/securitySingle sign-on (card)Missing here
Link SSO setup and troubleshooting from the Single sign-on card on /security

Ticket

Paste this into your ticketing tool.

Link SSO setup and troubleshooting from the Single sign-on card on /security

Who needs it: IT admins managing single sign-on
Section: /security › Single sign-on (card)

What is missing:
- The Single sign-on card doesn't say where to find setup or troubleshooting help.
- Supported identity providers and sign-in protocol details are not named.

Where: Update this section: extend the "Single sign-on" card in "Security and control, built into every hub".

What to do:
1. Confirm with engineering which identity providers and sign-in protocols are supported.
2. Add those to the Single sign-on card with a link to the new SSO guide on /resources.

Done when: The Single sign-on card on /security names supported identity providers and links to the SSO troubleshooting guide.
Depends on: Add a single sign-on troubleshooting guide to /resources

From: conversation 150d8bc87ad3, question 1: "SSO sign-in fails and says the assertion expired. What's wrong?"
Who needs it: IT admins managing single sign-on
What is missing
  • The Single sign-on card doesn't say where to find setup or troubleshooting help.
  • Supported identity providers and sign-in protocol details are not named.
Where
Update this section: extend the "Single sign-on" card in "Security and control, built into every hub".
What to do
  1. Confirm with engineering which identity providers and sign-in protocols are supported.
  2. Add those to the Single sign-on card with a link to the new SSO guide on /resources.
Done when: The Single sign-on card on /security names supported identity providers and links to the SSO troubleshooting guide.
Depends on: “Add a single sign-on troubleshooting guide to /resources”
Answer full page
An expired assertion is one of the usual causes of failed SSO sign-ins, and the troubleshooting guide walks through what to check. You'll find the details and a link to the docs below.
Sections in the answer pageStatus
/resourcesGuides to get you startedMissing here
/securitySingle sign-on (card)Missing here

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.