From 9cfb04417896ceb5328e3dd8457af1efb66946ad Mon Sep 17 00:00:00 2001
From: Sheen Capadngan <sheensantoscapadngan@gmail.com>
Date: Thu, 28 Nov 2024 20:41:30 +0800
Subject: [PATCH] misc: removed outdated faq section

---
 docs/documentation/platform/scim/overview.mdx | 15 ---------------
 1 file changed, 15 deletions(-)

diff --git a/docs/documentation/platform/scim/overview.mdx b/docs/documentation/platform/scim/overview.mdx
index c29241e49..5b8507961 100644
--- a/docs/documentation/platform/scim/overview.mdx
+++ b/docs/documentation/platform/scim/overview.mdx
@@ -24,18 +24,3 @@ SCIM providers:
 - [Okta SCIM](/documentation/platform/scim/okta)
 - [Azure SCIM](/documentation/platform/scim/azure)
 - [JumpCloud SCIM](/documentation/platform/scim/jumpcloud)
-
-**FAQ**
-
-<AccordionGroup>
-  <Accordion title="Why do SCIM-provisioned users have to finish setting up their account?">
-    Infisical's SCIM implementation accounts for retaining the end-to-end
-    encrypted architecture of Infisical because we decouple the
-    **authentication** and **decryption** steps in the platform. For this
-    reason, SCIM-provisioned users are initialized but must finish setting up
-    their account when logging in the first time by creating a master
-    encryption/decryption key. With this implementation, IdPs and SCIM providers
-    cannot and will not have access to the decryption key needed to decrypt your
-    secrets.
-  </Accordion>
-</AccordionGroup>