POST IA: Fix redirects (#2637)

Co-authored-by: Alexis Aguilar <[email protected]>

Author: SarahSoutoul

docs/guides/secure/session-tasks.mdx renamed to docs/guides/configure/session-tasks.mdx

@@ -92,14 +92,14 @@ The following steps outline the sign-in process:
 
 Session tasks require users to complete specific actions after authentication, such as selecting an organization. These tasks ensure that users meet all requirements before gaining full access to your application.
 
-For detailed information about configuring and implementing session tasks, see the [session tasks overview](/docs/guides/secure/session-tasks).
+For detailed information about configuring and implementing session tasks, see the [session tasks overview](/docs/guides/configure/session-tasks).
 
 #### Steps to handle session tasks
 
 After completing the sign-up or sign-in process, you should check if the user has any pending tasks:
 
 1. **Check for pending tasks**: Use the `navigate` parameter in [`setActive()`](/docs/reference/javascript/types/set-active-params) to access [`Session.currentTask`](/docs/reference/javascript/types/session-task) and check for pending session tasks.
-1. **Handle the task**: If a task exists, build UI to guide the user through completing the required action based on the task type. See the [available task types](/docs/guides/secure/session-tasks#available-tasks) to understand what actions may be required.
+1. **Handle the task**: If a task exists, build UI to guide the user through completing the required action based on the task type. See the [available task types](/docs/guides/configure/session-tasks#available-tasks) to understand what actions may be required.
 1. **Complete the flow**: Once all required tasks are completed, the session becomes fully `active` and the user can access protected content.
 
 You can build your own UI to handle specific task types. For example, if the task is `choose-organization`, you can create a [custom organization creation component](/docs/guides/development/custom-flows/organizations/create-organizations) to allow users to create or select an organization before proceeding.

docs/guides/development/custom-flows/overview.mdx

@@ -60,7 +60,7 @@ In the Clerk Dashboard, there are two types of workspaces:
 - **Personal account**: A personal account/workspace is a user's unique, individual space, independent of any organization.
 - **Organization workspace**: An organization workspace is owned and managed by an organization, which can have multiple members, also known as collaborators. The organization workspace that a user is currently viewing is called the [active organization](/docs/guides/organizations/overview#active-organization).
 
-Most multi-tenant applications want every user to be part of an organization rather than operating in an isolated personal account. Accordingly, **personal accounts are disabled by default** once you enable organizations. After signing up, [a user must create or join an organization before they can proceed](/docs/guides/secure/session-tasks).
+Most multi-tenant applications want every user to be part of an organization rather than operating in an isolated personal account. Accordingly, **personal accounts are disabled by default** once you enable organizations. After signing up, [a user must create or join an organization before they can proceed](/docs/guides/configure/session-tasks).
 
 To enable personal accounts for your application, toggle **Allow personal accounts** in the [**Organizations Settings**](https://dashboard.clerk.com/last-active?path=organizations-settings) page.
 
@@ -71,7 +71,7 @@ To enable personal accounts for your application, toggle **Allow personal accoun
 
 When a user is a member of an organization, they can switch between different organizations. The organization workspace that a user is currently viewing is called the **active organization**. The active organization determines which organization-specific data the user can access and which role and related permissions they have within the organization.
 
-When personal accounts are disabled (the default), users must select or create an organization to continue. This is handled automatically in the [session tasks flow](/docs/guides/secure/session-tasks).
+When personal accounts are disabled (the default), users must select or create an organization to continue. This is handled automatically in the [session tasks flow](/docs/guides/configure/session-tasks).
 
 When personal accounts are enabled, users initially sign in to their personal account with **no** active organization set. The easiest way to allow users to set an organization as active is to use the [`<OrganizationSwitcher />`](/docs/reference/components/organization/organization-switcher) component. If the prebuilt components don't meet your specific needs or if you require more control over the logic, you can also use the `setActive()` method, which is returned by the [`useOrganizationList()`](/docs/reference/hooks/use-organization-list) hook. If you aren't using hooks, you can access the `setActive()` method from the [`Clerk`](/docs/reference/javascript/clerk#set-active) object.
 

docs/guides/organizations/overview.mdx

@@ -315,7 +315,7 @@
                   },
                   {
                     "title": "Tasks after sign-up/sign-in",
-                    "href": "/docs/guides/secure/session-tasks"
+                    "href": "/docs/guides/configure/session-tasks"
                   }
                 ]
               ]

docs/manifest.json

@@ -71,7 +71,7 @@ type SessionStatus =
 | - | - |
 | `abandoned` | The session was abandoned client-side. |
 | `active` | The session is valid and all activity is allowed. |
-| `pending` | The user has signed in but hasn't completed [session tasks](/docs/guides/secure/session-tasks). |
+| `pending` | The user has signed in but hasn't completed [session tasks](/docs/guides/configure/session-tasks). |
 | `ended` | The user signed out of the session, but the `Session` remains in the `Client` object. |
 | `expired` | The period of allowed activity for this session has passed. |
 | `removed` | The user signed out of the session and the `Session` was removed from the `Client` object. |

docs/reference/backend/sessions/get-session-list.mdx

@@ -114,7 +114,7 @@ All sessions that are **expired**, **removed**, **replaced**, **ended** or **aba
   - `currentTask`
   - <code>[SessionTask](/docs/reference/javascript/types/session-task) | null</code>
 
-  The current pending task for the session. Read more about [session tasks](/docs/guides/secure/session-tasks).
+  The current pending task for the session. Read more about [session tasks](/docs/guides/configure/session-tasks).
 </Properties>
 
 ## Methods

docs/reference/javascript/session.mdx

@@ -24,7 +24,7 @@ type SessionStatus =
 | - | - |
 | `abandoned` | The session was abandoned client-side. |
 | `active` | The session is valid and all activity is allowed. |
-| `pending` | The user has signed in but hasn't completed [session tasks](/docs/guides/secure/session-tasks). |
+| `pending` | The user has signed in but hasn't completed [session tasks](/docs/guides/configure/session-tasks). |
 | `ended` | The user signed out of the session, but the [`Session`][session-ref] remains in the [`Client`][client-ref] object. |
 | `expired` | The period of allowed activity for this session has passed. |
 | `removed` | The user signed out of the session and the [`Session`][session-ref] was removed from the [`Client`][client-ref] object. |

docs/reference/javascript/types/session-status.mdx

@@ -4,7 +4,7 @@ description: The SessionTask interface represents the current pending task of a
 sdk: js-frontend
 ---
 
-An interface that represents the current [pending task](/docs/guides/secure/session-tasks) of a session.
+An interface that represents the current [pending task](/docs/guides/configure/session-tasks) of a session.
 
 ## Properties
 

docs/reference/javascript/types/session-task.mdx

@@ -1,17 +1,22 @@
 [
   {
     "source": "/docs/authentication/saml/:path*",
-    "destination": "/docs/authentication/enterprise-connections/:path*",
+    "destination": "/docs/guides/configure/auth-strategies/enterprise-connections/:path*",
+    "permanent": true,
+  },
+  {
+    "source": "/docs/authentication/enterprise-connections/:path*",
+    "destination": "/docs/guides/configure/auth-strategies/enterprise-connections/:path*",
     "permanent": true,
   },
   {
     "source": "/docs/components/customization/:path*",
-    "destination": "/docs/customization/:path*",
+    "destination": "/docs/guides/customizing-clerk/:path*",
     "permanent": true,
   },
   {
     "source": "/docs/customization/account-portal/:path*",
-    "destination": "/docs/account-portal/:path*",
+    "destination": "/docs/guides/customizing-clerk/account-portal/:path*",
     "permanent": true,
   },
   {
@@ -20,23 +25,18 @@
     "permanent": true,
   },
   {
-    "source": "/docs/integrations/webhooks/:path*",
-    "destination": "/docs/webhooks/:path*",
+    "source": "/docs/customization/elements/:path*",
+    "destination": "/docs/guides/customizing-clerk/elements/:path*",
     "permanent": true,
   },
   {
-    "source": "/docs/reference/:path/custom-signup-signin-pages",
-    "destination": "/docs/reference/:path/custom-sign-in-or-up-page",
+    "source": "/docs/integrations/webhooks/:path*",
+    "destination": "/docs/guides/development/webhooks/:path*",
     "permanent": true,
   },
   {
     "source": "/docs/backend-requests/versioning/:path*",
-    "destination": "/docs/versioning/:path*",
-    "permanent": true,
-  },
-  {
-    "source": "/docs/reference/tanstack-start/:path*",
-    "destination": "/docs/reference/tanstack-react-start/:path*",
+    "destination": "/docs/guides/development/upgrading/versioning/:path*",
     "permanent": true,
   },
   {
@@ -49,21 +49,6 @@
     "destination": "/docs/:sdk/reference/hooks/:path*",
     "permanent": true,
   },
-  {
-    "source": "/docs/authentication/:path*",
-    "destination": "/docs/guides/configure/auth-strategies/:path*",
-    "permanent": true,
-  },
-  {
-    "source": "/docs/integrations/:path*",
-    "destination": "/docs/guides/development/integrations/:path*",
-    "permanent": true,
-  },
-  {
-    "source": "/docs/customization/elements/:path*",
-    "destination": "/docs/guides/customizing-clerk/elements/:path*",
-    "permanent": true,
-  },
   {
     "source": "/docs/references/:path*",
     "destination": "/docs/reference/:path*",