From 99926b24f316c11969fc21a9152db6111d33d57b Mon Sep 17 00:00:00 2001
From: rodolfoBee <64906376+rodolfoBee@users.noreply.github.com>
Date: Thu, 10 Jul 2025 09:39:06 +0200
Subject: [PATCH] remove 20h mention

---
 docs/organization/authentication/sso/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/organization/authentication/sso/index.mdx b/docs/organization/authentication/sso/index.mdx
index b89847f2b28c6..731bcc1224a21 100644
--- a/docs/organization/authentication/sso/index.mdx
+++ b/docs/organization/authentication/sso/index.mdx
@@ -24,7 +24,7 @@ Every member who creates a new account via SSO will be given global organization
 
 Our SSO implementation prioritizes security. We aggressively monitor linked accounts and will disable them if there's any reasonable sign that the account’s access may have been revoked. Generally this will be transparent to you, but if the provider is functioning in an unexpected way you may experience more frequent re-authorization requests.
 
-Sessions last for [Django's default session length](https://docs.djangoproject.com/en/1.11/topics/http/sessions/#using-cookie-based-sessions), which is two weeks. For individual organizations with single sign-on, we expire organization access after one day (20 hours).
+Sessions last for [Django's default session length](https://docs.djangoproject.com/en/1.11/topics/http/sessions/#using-cookie-based-sessions), which is two weeks.
 
 ## Providers