Documentation updated for redirect support in partial authentication

authentication-personalization/authentication-setup.mdx

@@ -17,10 +17,14 @@
 
 Choose between full and partial authentication modes based on your access control needs.
 
 **Full authentication**: All pages are protected. Users must log in before accessing any content.
 
 **Partial authentication**: Some pages are publicly viewable while others require authentication. Users can browse public content freely and authenticate only when accessing protected pages.
 
+<Info>
+Partial authentication supports redirects for unauthenticated users. When an unauthenticated user visits a redirect source path, the system will check the destination page's authentication requirements and return the appropriate access metadata.
+</Info>
+
 When configuring any handshake method below, you'll select either **Full authentication** or **Partial authentication** in your dashboard settings.
 
 ## Configuring authentication
@@ -30,7 +34,7 @@
 <Tabs>
 <Tab title="Password">
 <Info>
 Password authentication provides access control only and does **not** support content personalization.
 </Info>
 
 ### Prerequisites
@@ -54,9 +58,9 @@
 
 ## Example
 
 Your documentation is hosted at `docs.foo.com` and you need basic access control without tracking individual users. You want to prevent public access while keeping setup simple. 
 
 **Create a strong password** in your dashboard. **Share credentials** with authorized users. That's it!
 </Tab>
 <Tab title="Mintlify Dashboard">
 ### Prerequisites
@@ -81,17 +85,17 @@
 
 ### Example
 
 Your documentation is hosted at `docs.foo.com` and your team uses the dashboard to edit your docs. You want to restrict access to team members only.
 
 **Enable Mintlify authentication** in your dashboard settings.
 
 **Verify team access** by checking that all team members are added to your organization.
 </Tab>
 <Tab title="OAuth 2.0">
 ### Prerequisites
 
 * An OAuth or OIDC server that supports the Authorization Code Flow.
 * Ability to create an API endpoint accessible by OAuth access tokens (optional, to enable personalization features).
 
 ### Implementation
 
@@ -100,13 +104,13 @@
     1. In your dashboard, go to [Authentication](https://dashboard.mintlify.com/settings/deployment/authentication).
     2. Select **Full Authentication** or **Partial Authentication**.
     3. Select **OAuth** and configure these fields:
       * **Authorization URL**: Your OAuth endpoint.
       * **Client ID**: Your OAuth 2.0 client identifier.
       * **Client Secret**: Your OAuth 2.0 client secret.
       * **Scopes**: Permissions to request. Copy the **entire** scope string (for example, for a scope like `provider.users.docs`, copy the complete `provider.users.docs`). Use multiple scopes if you need different access levels.
       * **Token URL**: Your OAuth token exchange endpoint.
       * **Info API URL** (optional): Endpoint to retrieve user info for personalization. If omitted, the OAuth flow will only be used to verify identity and the user info will be empty.
       * **Logout URL**: The native logout URL for your OAuth provider. If your provider has a `returnTo` or similar parameter, point it back to your docs URL.
     4. Select **Save changes**.
   </Step>
   <Step title="Configure your OAuth server.">
@@ -124,7 +128,7 @@
 
 ### Example
 
 Your documentation is hosted at `foo.com/docs` and you have an existing OAuth server at `auth.foo.com` that supports the Authorization Code Flow.
 
 **Configure your OAuth server details** in your dashboard:
 - **Authorization URL**: `https://auth.foo.com/authorization`
@@ -142,7 +146,7 @@
     "firstName": "Jane",
     "lastName": "Doe"
   },
   "groups": ["engineering", "admin"]
 }
 ```
 
@@ -243,7 +247,7 @@
 
 ### Redirecting unauthenticated users
 
 When an unauthenticated user tries to access a protected page, their intended destination is preserved in the redirect to your login URL:
 
 1. User attempts to visit a protected page: `https://docs.foo.com/quickstart`.
 2. Redirect to your login URL with a redirect query parameter: `https://foo.com/docs-login?redirect=%2Fquickstart`.
@@ -254,7 +258,7 @@
 
 ## Making pages public
 
 When using partial authentication, all pages are protected by default. You can make specific pages viewable without authentication at the page or group level with the `public` property.
 
 ### Page level
 

settings.mdx

@@ -219,7 +219,7 @@
           Font weight, such as 400, 700. Variable fonts support precise weights such as 550.
         </ResponseField>
         <ResponseField name="source" type="string (uri)">
           URL to your font source, such as https://mintlify-assets.b-cdn.net/fonts/Hubot-Sans.woff2. [Google Fonts](https://fonts.google.com) are loaded automatically when you specify a Google Font `family` name, so no source URL is needed.
         </ResponseField>
         <ResponseField name="format" type="&quot;woff&quot; | &quot;woff2&quot;">
           Font file format.
@@ -495,7 +495,7 @@
 
   <Expandable title="Interaction">
     <ResponseField name="drilldown" type="boolean">
       Control automatic navigation behavior when selecting navigation groups. Set to `true` to force navigation to the first page when a navigation group is expanded. Set to `false` to prevent navigation and only expand or collapse the group. Leave unset to use the theme's default behavior.
     </ResponseField>
   </Expandable>
 </ResponseField>
@@ -572,9 +572,13 @@
       Destination path to redirect to. Example: `/new-page`
     </ResponseField>
     <ResponseField name="permanent" type="boolean">
       Whether to use a permanent redirect (301). Defaults to `true`.
     </ResponseField>
   </Expandable>
+
+  <Note>
+    **Partial authentication support**: When using [partial authentication](/authentication-personalization/authentication-setup#authentication-modes), redirects work for unauthenticated users. If an unauthenticated user visits a redirect source path, the system checks the destination page's authentication requirements and returns the appropriate access metadata. Wildcard redirects are not supported with partial authentication.
+  </Note>
 </ResponseField>
 
 <ResponseField name="contextual" type="object">
@@ -583,13 +587,13 @@
   <Expandable title="Contextual">
     <ResponseField name="options" type="array of &quot;copy&quot; | &quot;view&quot; | &quot;chatgpt&quot; | &quot;claude&quot; | &quot;perplexity&quot; | &quot;mcp&quot; | &quot;cursor&quot; | &quot;vscode&quot;" required>
       Actions available in the contextual menu. The first option appears as the default.
       - `copy`: Copy the current page as Markdown to the clipboard.
       - `view`: View the current page as Markdown in a new tab.
       - `chatgpt`: Send the current page content to ChatGPT.
       - `claude`: Send the current page content to Claude.
       - `perplexity`: Send the current page content to Perplexity.
       - `mcp`: Copies your MCP server URL to the clipboard.
       - `cursor`: Installs your hosted MCP server in Cursor.
       - `vscode`: Installs your hosted MCP server in VSCode.
 
       <img src="/images/page-context-menu.png" alt="Contextual Menu" className="rounded-xl" />
@@ -602,7 +606,7 @@
   </Expandable>
 </ResponseField>
 
 ### API Configurations
 
 <ResponseField name="api" type="object">
   API documentation and interactive playground settings.
@@ -698,10 +702,10 @@
   </Expandable>
 </ResponseField>
 
 ### SEO and search
 
 <ResponseField name="seo" type="object">
   SEO indexing configurations.
 
   <Expandable title="Seo">
     <ResponseField name="metatags" type="object">
@@ -937,7 +941,7 @@
       404 "Page not found" error handling.
       <Expandable title="404">
         <ResponseField name="redirect" type="boolean">
           Whether to automatically redirect to the home page when a page is not
           found.
         </ResponseField>
         <ResponseField name="title" type="string">
@@ -1493,7 +1497,7 @@
 
 </CodeGroup>
 
 If you already have the CLI installed, make sure it is up to date:
 
 ```bash
 mint update
@@ -1507,7 +1511,7 @@
 mint upgrade
 ```
 
 This command will create a `docs.json` file from your existing `mint.json`. Review the generated file to ensure all settings are correct.
 </Step>
 <Step title="Delete your mint.json file">
 After verifying your `docs.json` is configured properly, you can safely delete your old `mint.json` file.