Merge pull request #525 from mistralai/sync/latest

Sync docs to v1.1.19

Author: grebett

pnpm-lock.yaml

@@ -10,10 +10,11 @@ API keys authenticate your requests to the Mistral API. Each key is scoped to a
 <SectionTab as="h1" sectionId="creating-keys">Create an API key</SectionTab>
 
 1. <AppLink href="https://console.mistral.ai/api-keys" app="studio">API keys</AppLink>.
-2. Click **Create new key**.
-3. Optionally set a **name** (e.g., "Production pipeline") and an **expiration date**.
-4. Click **Create new key**.
-5. Copy the key immediately.
+2. Click `Create new key`.
+3. Optionally set a `Name` (for example, `Production pipeline`) and an `Expiration` date.
+4. Choose a `Connector access scope`.
+5. Click `Create new key`.
+6. Copy the key immediately.
 
 :::warning
 **The full key is shown only once**. After you close the dialog, you can't retrieve it. Store the key securely in a password manager or secrets vault. Don't share it or commit it to version control.
@@ -38,10 +39,23 @@ export MISTRAL_API_KEY="your-api-key"
 
 <SectionTab as="h1" sectionId="workspace-scoping">Workspace scoping</SectionTab>
 
-API keys are **scoped to the Workspace** where they were created. Resources created with a key (like datasets, batch jobs, etc.) are visible to all members of that Workspace.
+API keys are **scoped to the Workspace** where they were created. Resources created with a key, such as datasets and batch jobs, are visible to all members of that Workspace.
 
 To use different keys for different environments (development, staging, production), create separate [Workspaces](/admin/security-access/organization).
 
+<SectionTab as="h1" sectionId="connector-access-scope">Connector access scope</SectionTab>
+
+When you create an API key, use `Connector access scope` to control which Connectors the key can use:
+
+| Scope | Access |
+|-------|--------|
+| `Shared connectors only` | Access only Connectors shared with the Workspace, not your private Connectors. |
+| `Private and shared connectors` | Access both your private Connectors and the Connectors shared with the Workspace. |
+
+:::tip
+Use `Shared connectors only` for automation. Use `Private and shared connectors` only when the application needs private Connectors owned by the key creator.
+:::
+
 <SectionTab as="h1" sectionId="key-management">Key management</SectionTab>
 
 - **Rotate keys** regularly. Create a new key, update your applications, then delete the old one.

public/admin/security-access/api-keys.md

@@ -40,6 +40,7 @@ From the Admin Panel, administrators can:
 - **Organization**: rename, configure settings, view the Organization ID
 - **Members**: invite users, assign seats and roles, remove members
 - **Workspaces**: create isolated environments with independent API keys and usage tracking
+- **Connectors**: connect organization-level bots and control Connector tool access
 - **Access**: configure SSO and Email Domain Authentication
 - **Billing**: manage payment methods, subscriptions, and invoices
 - **Usage limits**: set spending caps per Workspace

public/admin/security-access/back-office.md

@@ -16,6 +16,7 @@ At the Organization level, administrators can manage:
 - **Billing** for all Workspaces
 - **Subscriptions** (Vibe and Studio)
 - **Members** and role assignments
+- **Connectors** and organization-level app connections
 - **Security** settings (SSO, domain authentication)
 - **Privacy** and data handling preferences
 - **Audit logs** (Enterprise)

public/admin/security-access/organization.md

@@ -60,11 +60,11 @@ Control who has access to each workspace independently.
   <TableBody>
     <TableRow>
       <TableCell>**Admin**</TableCell>
-      <TableCell>Full workspace control: manage members, keys, settings</TableCell>
+      <TableCell>Full workspace control: manage members, keys, settings, view usage</TableCell>
     </TableRow>
     <TableRow>
       <TableCell>**Member**</TableCell>
-      <TableCell>Use API keys, view usage: no management access</TableCell>
+      <TableCell>Use API keys</TableCell>
     </TableRow>
   </TableBody>
 </Table>

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

@@ -23,18 +23,21 @@ By the end you will have a working API key ready to use in your first request.
 <SectionTab as="h2" sectionId="step-1">Step 1: Generate an API key</SectionTab>
 
 1. Open the <AppLink href="https://console.mistral.ai" app="studio">Studio console</AppLink>.
-2. Navigate to **API Keys** in the left sidebar.
-3. Click **Create new key**.
+2. Navigate to `API Keys` in the left sidebar.
+3. Click `Create new key`.
 
 ![Click Create new key](/assets/quickstarts/studio/new-key-button.png)
 
-4. Add a **Name** to identify the key (for example, "First test key").
-5. Set an **Expiration** date. Regular rotation improves security.
+1. Add a `Name` to identify the key (for example, `First test key`).
+2. Set an `Expiration` date. Regular rotation improves security.
+3. Choose a `Connector access scope`:
+   - `Shared connectors only`: access only Connectors shared with the Workspace, not your private Connectors.
+   - `Private and shared connectors`: access both your private Connectors and the Connectors shared with the Workspace.
 
 ![Configure the API key with optional name and expiration date](/assets/quickstarts/studio/new-key-modal.png)
 
-6. Click **Create new key**.
-7. Copy the key immediately and store it in a secure location (password manager or secrets vault).
+1. Click `Create new key`.
+2. Copy the key immediately and store it in a secure location (password manager or secrets vault).
 
 :::warning
 The full key appears only once. You cannot retrieve it after closing the confirmation dialog.

public/getting-started/quickstarts/studio/activate-and-generate-api-key.md

@@ -392,7 +392,7 @@ Dragon
 In this example, the model generates a response considering only the top tokens that cumulatively reach a 50% probability threshold. This ensures that the output keeps some uniform diversity while still taking only the best tokens, in this case only 2 tokens reach the 50% threshold.
   </ExplorerTab>
   <ExplorerTab value="penalties" label="Penalties">
-    Presence and Frequency Penalties are parameters that repetition, it allows you to control the diversity of the generated text.
+    Presence and frequency penalties are parameters that penalize repetition. They let you control the diversity of generated text.
 
 <SectionTab as="h2" variant="secondary" sectionId="presence-penalty">Presence Penalty</SectionTab>
 

public/models/best-practices/sampling.md

@@ -24,9 +24,9 @@ We provide a variety of different **types** of tools agents can use.
 |[Web Search](/studio-api/agents/agent-tools/websearch)| Built-in. Search the web for up-to-date information not in the agent's knowledge.|
 |[Code Interpreter](/studio-api/agents/agent-tools/code_interpreter)| Built-in. Run code and generate plots, useful for data analysis, visualization, or sandboxed execution.|
 |[Image Generation](/studio-api/agents/agent-tools/image_generation)| Built-in. Generate images based on a prompt or description.|
-|[Document Library](/studio-api/knowledge-rag/libraries#connecting-libraries-to-agents)| Built-in. Search through documents uploaded to your [Libraries](/studio-api/knowledge-rag/libraries), enabling RAG to answer questions based on specific information.|
+|[Document Library](/studio-api/libraries#connecting-libraries-to-agents)| Built-in. Search through documents uploaded to your [Libraries](/studio-api/libraries), enabling RAG to answer questions based on specific information.|
 |[Function Calling](/studio-api/agents/agent-tools/function-calling)| Custom local tools: functions defined in your environment that can be called by the agent. Execution happens locally.|
-|[Connectors](/studio-api/knowledge-rag/connectors)| Register MCP servers as managed Connectors. Tools are discovered automatically and executed server-side.|
+|[Connectors](/studio-api/connectors)| Register MCP servers as managed Connectors. Tools are discovered automatically and executed server-side.|
 
 <SectionTab as="h1" sectionId="built-in-tools">Built-in tools</SectionTab>
 

public/studio-api/agents/agent-tools.md

@@ -11,7 +11,7 @@ The core of an agent relies on its tool usage capabilities, enabling it to use a
 
 Built into our API, we provide [built-in tools](/studio-api/agents/agent-tools#built-in-tools) such as `websearch`, `code_interpreter`, `image_generation` and `document_library`. However, you can also use standard function tool calling by defining a JSON schema for your function.
 
-You can also register MCP servers as [Connectors](/studio-api/knowledge-rag/connectors) to use external tools in conversations and Agents.
+You can also register MCP servers as [Connectors](/studio-api/connectors) to use external tools in conversations and Agents.
 
 For more information regarding function calling, we recommend to visit our [function calling docs](/studio-api/conversations/function-calling).
 

public/studio-api/agents/agent-tools/function-calling.md

@@ -268,5 +268,5 @@ Below we will explain the different outputs of the response of the previous snip
 
 <SectionTab as="h3" variant="secondary" sectionId="more">More</SectionTab>
 
-Another tool that uses references is the Document Library tool — see the [Libraries guide](/studio-api/knowledge-rag/libraries#connecting-libraries-to-agents) for details.
+Another tool that uses references is the Document Library tool — see the [Libraries guide](/studio-api/libraries#connecting-libraries-to-agents) for details.
 For more on citations, see the [citations guide](/studio-api/conversations/citations).