chore: sync docs to v1.1.23

Author: grebett

public/getting-started/platform-overview.md

@@ -73,7 +73,7 @@ Admin is the control plane for IT, security, and finance teams. Manage your orga
 <CtaButton href="https://admin.mistral.ai">Open Admin</CtaButton>
 
 <UsefullLinkContainer>
-  <LinkCard href="/admin/security-access/back-office" title="Admin documentation" />
+  <LinkCard href="/admin/set-up-organization/create-organization" title="Admin documentation" />
   <LinkCard href="/#quickstarts" title="Admin quickstarts" />
 </UsefullLinkContainer>
 

public/getting-started/quickstarts/admin/create-organization.md

@@ -42,7 +42,7 @@ Already have an account without an organization? Open <AppLink href="https://adm
 
 Team members can't generate working API keys until billing is active.
 
-Open <AppLink href="https://admin.mistral.ai/organization/billing" app="admin">Subscriptions › Billing</AppLink>, click **Add payment method**, and connect your card or cloud marketplace account. Optionally set a **Monthly spending limit** before saving.
+Open <AppLink href="https://admin.mistral.ai/organization/billing" app="admin" path={["Subscriptions", "Billing"]} />, click **Add payment method**, and connect your card or cloud marketplace account. Optionally set a **Monthly spending limit** before saving.
 
 Billing takes 2–3 minutes to take effect. If team members report inactive API keys right after, ask them to wait and retry.
 

public/getting-started/quickstarts/admin/manage-workspaces.md

@@ -94,7 +94,7 @@ Never commit API keys to source control. Use environment variables or a secrets
 
 Prevent unexpected costs by setting monthly spending limits per workspace.
 
-1. Open <AppLink href="https://admin.mistral.ai/organization/billing" app="admin">Subscriptions › Billing</AppLink>.
+1. Open <AppLink href="https://admin.mistral.ai/organization/billing" app="admin" path={["Subscriptions", "Billing"]} />.
 2. Under the workspace, click **Set limit**.
 3. Enter a monthly budget in USD: for example, `$500`.
 4. When the workspace hits the limit, API requests return `429 Too Many Requests` until the next billing cycle.

public/getting-started/quickstarts/developer/first-api-request.md

@@ -176,7 +176,7 @@ The terminal prints a short description of Mistral AI. If it doesn't, check the
     <TableRow>
       <TableCell>`402 Payment Required`</TableCell>
       <TableCell>No payment method on account</TableCell>
-      <TableCell>Add one at <AppLink href="https://admin.mistral.ai/organization/billing" app="admin">Subscriptions › Billing</AppLink></TableCell>
+      <TableCell>Add one at <AppLink href="https://admin.mistral.ai/organization/billing" app="admin" path={["Subscriptions", "Billing"]} /></TableCell>
     </TableRow>
     <TableRow>
       <TableCell>`429 Too Many Requests`</TableCell>

public/img/admin_enterprise_hierarchy.svg

@@ -26,7 +26,7 @@ Studio gives you programmatic access to Mistral models for text generation, agen
 
 <SectionTab as="h1" sectionId="getting-started-api">Getting started with the API</SectionTab>
 
-1. **Create an API key** in the console or through the [API keys](/admin/security-access/api-keys) page in Admin.
+1. **Create an API key** in the console or through the [API keys](/admin/identity-access/api-keys) page in Admin.
 2. **Send your first request**: follow the [send your first API request](/getting-started/quickstarts/developer/first-api-request) quickstart to make a chat completion call in Python or TypeScript.
 
 :::tip

public/img/admin_overview.svg

@@ -11,7 +11,7 @@ This section explains the building blocks of Mistral Workflows and how they fit
 
 <SectionTab as="h2" sectionId="mental-model">The mental model</SectionTab>
 
-Everything starts at the **Workflows API**: the orchestrator you call to start, query, and signal runs. For full endpoint details, see the [API reference](/api/endpoint/workflows).
+Everything starts at the **Workflows API**: the orchestrator you call to start, query, and signal runs. For full endpoint details, see the [API reference](/api/endpoint/beta/workflows).
 
 Your code lives outside the API, in **Workers**: processes you deploy that connect outbound to the API and pull work from it. The code a worker runs splits in two:
 

public/studio-api/overview.md

@@ -43,7 +43,7 @@ Admins can:
 A deployment can have multiple credentials to support key rotation or multi-worker setups.
 
 :::tip
-Manage your API keys in the [API keys](/admin/security-access/api-keys) section of the admin panel.
+Manage your API keys in the [API keys](/admin/identity-access/api-keys) section of the admin panel.
 :::
 
 <SectionTab as="h1" sectionId="registering-an-obo-workflow">Registering an OBO workflow</SectionTab>

public/studio-api/workflows/getting-started/core_concepts.md

@@ -8,7 +8,7 @@ sidebar_position: 9
 Your Mistral account belongs to one or more **Organizations**, and each Organization contains one or more **Workspaces**. A Workspace is an **isolation boundary**: use it to keep resources separate between departments, projects, or environments. It is not a team-management container.
 
 :::info
-Workspaces are shared across Vibe, Studio, and the Admin Panel: the same Workspace entity is visible in all three. In Vibe Work, switching Workspace changes which scope you're working in. See [Organizations and Workspaces](/admin/security-access/organization) for the admin view.
+Workspaces are shared across Vibe, Studio, and the Admin Panel: the same Workspace entity is visible in all three. In Vibe Work, switching Workspace changes which scope you're working in. See [Organizations and Workspaces](/admin/workspaces/organization-vs-workspaces) for the admin view.
 :::
 
 <SectionTab as="h2" sectionId="switcher">Switch from the sidebar</SectionTab>
@@ -54,7 +54,7 @@ Some Vibe Work behavior is configured per Workspace by Organization Admins:
 - **User access and roles**: who can join the Workspace and at what role.
 - **Usage metrics**: per-Workspace usage tracking.
 
-If a feature is missing or behaves differently between Workspaces, this is usually why. Reach out to your Organization admin to adjust settings, or see [Organizations and Workspaces](/admin/security-access/organization) for the configuration details.
+If a feature is missing or behaves differently between Workspaces, this is usually why. Reach out to your Organization admin to adjust settings, or see [Organizations and Workspaces](/admin/workspaces/organization-vs-workspaces) for the configuration details.
 
 :::tip
 More granular sharing of individual resources with specific users or groups, without requiring a Workspace switch, is on the roadmap.