remove SSO and personalization info

Author: ethanpalm

protected-pages/overview.mdx

@@ -2,7 +2,7 @@
 title: "Overview"
 description: "Control access to your documentation"
 icon: "badge-info"
-keywords: ["auth"]
+keywords: ["auth", "authentication"]
 ---
 
 <Info>
@@ -16,8 +16,6 @@ You can make all of your content private or control access on a page-by-page bas
 
 ## Handshake methods
 
-TODO: verify that SSO is still an option
-
 **JSON Web Token (JWT)**: Custom system where you manage user tokens with full control over the login flow.
 
 - Pros of JWT:
@@ -53,77 +51,3 @@ TODO: verify that SSO is still an option
 - Cons of password:
   - Lose personalization features since there is no way to differentiate users with the same password.
   - Must change the password to revoke access.
-
-**Shared session**: Use the same session token as your dashboard to personalize content.
-
-- Pros of shared session:
-  - Users that are logged into your dashboard are automatically logged into your docs.
-  - User sessions are persistent so you can refresh data without requiring a new login.
-  - Minimal setup.
-- Cons of shared session:
-  - Your docs will make a request to your backend.
-  - You must have a dashboard that uses session authentication.
-  - CORS configuration is generally required.
-
-## Content customization
-
-TODO: this might all be moved
-
-When users are authenticated to your docs, you can customize their experience with dynamic content.
-
-### Dynamic `MDX` content
-
-Display dynamic content based on user information like name, plan, or organization.
-
-The `user` variable contains information sent to your docs from logged in users. See [Sending data](/protected-pages/sending-data) for more information.
-
-**Example**: Hello, {user.name ?? 'reader'}!
-
-```jsx
-Hello, {user.name ?? 'reader'}!
-```
-
-This feature is more powerful when you pair it with custom data about your users. For example, you can give different instructions based on a user's plan.
-
-**Example**: Authentication is an enterprise feature. {
-user.org === undefined
-? <>To access this feature, first create an account at the <a href="https://dashboard.mintlify.com/login">Mintlify dashboard</a>.</>
-: user.org.plan !== 'enterprise'
-? <>You are currently on the ${user.org.plan ?? 'free'} plan. To speak to our team about upgrading, <a href="mailto:[email protected]">contact our sales team</a>.</>
-: <>To request this feature for your enterprise org, <a href="mailto:[email protected]">contact our team</a>.</>
-}
-
-```jsx
-Authentication is an enterprise feature. {
-  user.org === undefined
-    ? <>To access this feature, first create an account at the <a href="https://dashboard.mintlify.com/login">Mintlify dashboard</a>.</>
-    : user.org.plan !== 'enterprise'
-      ? <>You are currently on the ${user.org.plan ?? 'free'} plan. To speak to our team about upgrading, <a href="mailto:[email protected]">contact our sales team</a>.</>
-      : <>To request this feature for your enterprise org, <a href="mailto:[email protected]">contact our team</a>.</>
-}
-```
-
-<Note>
-  The information in `user` is only available for logged in users. For logged
-  out users, the value of `user` will be `{}`. To prevent the page from crashing
-  for logged out users, always use optional chaining on your `user` fields. For
-  example, `{user.org?.plan}`.
-</Note>
-
-### API key prefilling
-
-Automatically populate API playground fields with user-specific values by returning matching field names in your user data. The field names in your user data must exactly match the names in the API playground for automatic prefilling to work.
-
-### Page visibility
-
-Restrict which pages are visible to your users by adding `groups` fields to your pages' frontmatter. By default, every page is visible to every user.
-
-Users will only see pages for `groups` that they are in.
-
-```mdx
----
-title: "Managing your users"
-description: "Adding and removing users from your organization"
-groups: ["admin"]
----
-```