diff --git a/product/admin/ai-clients.mdx b/product/admin/ai-clients.mdx index 1275feda..efdf4c8e 100644 --- a/product/admin/ai-clients.mdx +++ b/product/admin/ai-clients.mdx @@ -73,7 +73,7 @@ To change which types are allowed: -Go to **Settings > AI Connections**. +Go to **AI > C1 Gateway > Settings**. Edit **Allowed client types**. diff --git a/product/admin/c1-mcp.mdx b/product/admin/c1-mcp.mdx index ff45fbb7..b3bd3d5b 100644 --- a/product/admin/c1-mcp.mdx +++ b/product/admin/c1-mcp.mdx @@ -38,10 +38,10 @@ A Super Admin must enable AI connections in your tenant settings: -Navigate to **Settings** > **AI connections**. +Navigate to **AI** > **C1 Gateway** and open the **Settings** tab. -At the top of the **AI connections** page, click **Edit** and toggle **Enable AI connections** to on. +Find **AI connections**, click **Edit**, and toggle **Enable AI connections** to on. Click **Save**. @@ -304,7 +304,7 @@ Revoking a connection immediately prevents the AI assistant from accessing your ### Admin management -Super Admins can navigate to **Settings** > **AI connections** to view and revoke all connections across the tenant. +Super Admins can navigate to **AI** > **C1 Gateway** > **Connected clients** to view and revoke all connections across the tenant. ## System log events diff --git a/product/admin/enable-ai-access-management.mdx b/product/admin/enable-ai-access-management.mdx index 3f03a44e..6663751d 100644 --- a/product/admin/enable-ai-access-management.mdx +++ b/product/admin/enable-ai-access-management.mdx @@ -24,7 +24,7 @@ Enabling AIAM exposes the AIAM surfaces (MCP servers, tools, AI clients, AIAM au Log in to your C1 tenant as a Super Admin. -Navigate to **Settings > AI Connections**. +Navigate to **AI > C1 Gateway** and open the **Settings** tab. Click **Edit AI Connections**. @@ -58,7 +58,7 @@ To change which types are allowed: -In **Settings > AI Connections**, find **Allowed client types**. +In **AI > C1 Gateway > Settings**, find **Allowed client types**. Check the boxes for the types you want to permit. @@ -83,7 +83,7 @@ To change the defaults: -In **Settings > AI Connections**, find **Default tool classification**. +In **AI > MCP > Settings**, find **Default tool classification**. Select the state and classification to apply to newly-discovered tools. @@ -118,7 +118,7 @@ To change the thresholds: -In **Settings > AI Connections**, find **Client lifecycle**. +In **AI > C1 Gateway > Settings**, find **Client lifecycle**. Set the inactivity threshold for each state. @@ -141,7 +141,7 @@ The kill switch immediately revokes every AI client's access to every tool, acro -In **Settings > AI Connections**, find **Emergency kill switch**. +In **Settings > System management**, find **Emergency kill switch**. Click **Disable all AI access**. diff --git a/product/admin/mcp-server/apollo.mdx b/product/admin/mcp-server/apollo.mdx index 7d7bdd9a..c613e08c 100644 --- a/product/admin/mcp-server/apollo.mdx +++ b/product/admin/mcp-server/apollo.mdx @@ -73,7 +73,7 @@ Save your changes. C1 starts a sync that discovers the tools the Apollo server e After you register the server, C1 runs tool discovery against Apollo. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an Apollo tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/auth0.mdx b/product/admin/mcp-server/auth0.mdx index cd5d41d5..95137382 100644 --- a/product/admin/mcp-server/auth0.mdx +++ b/product/admin/mcp-server/auth0.mdx @@ -78,7 +78,7 @@ Save your changes. C1 starts a sync that discovers the tools the Auth0 server ex After you register the server, C1 runs tool discovery against Auth0. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an Auth0 tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/azure-devops.mdx b/product/admin/mcp-server/azure-devops.mdx index f3a8e1de..50680b1b 100644 --- a/product/admin/mcp-server/azure-devops.mdx +++ b/product/admin/mcp-server/azure-devops.mdx @@ -134,7 +134,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Azure DevOps. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an Azure DevOps tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/bitbucket.mdx b/product/admin/mcp-server/bitbucket.mdx index b656494f..82bfbf04 100644 --- a/product/admin/mcp-server/bitbucket.mdx +++ b/product/admin/mcp-server/bitbucket.mdx @@ -166,7 +166,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Bitbucket. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Bitbucket tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/box.mdx b/product/admin/mcp-server/box.mdx index 71121b5e..f587b7ce 100644 --- a/product/admin/mcp-server/box.mdx +++ b/product/admin/mcp-server/box.mdx @@ -100,7 +100,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Box. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Box tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/buildkite.mdx b/product/admin/mcp-server/buildkite.mdx index bc01468c..c6b9daca 100644 --- a/product/admin/mcp-server/buildkite.mdx +++ b/product/admin/mcp-server/buildkite.mdx @@ -81,7 +81,7 @@ Save your changes. C1 starts a sync that discovers the tools the Buildkite serve After you register the server, C1 runs tool discovery against Buildkite. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Buildkite tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/confluence.mdx b/product/admin/mcp-server/confluence.mdx index 17ffdd3d..a9a6c7be 100644 --- a/product/admin/mcp-server/confluence.mdx +++ b/product/admin/mcp-server/confluence.mdx @@ -85,7 +85,7 @@ Save your changes. The first time a user calls a Confluence tool from their AI c After you register the server, C1 runs tool discovery against Confluence. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Confluence tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/crowdstrike.mdx b/product/admin/mcp-server/crowdstrike.mdx index 290f928a..6a7745d5 100644 --- a/product/admin/mcp-server/crowdstrike.mdx +++ b/product/admin/mcp-server/crowdstrike.mdx @@ -85,7 +85,7 @@ Save your changes. C1 starts a sync that discovers the tools the CrowdStrike ser After you register the server, C1 runs tool discovery against CrowdStrike. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a CrowdStrike tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/datadog.mdx b/product/admin/mcp-server/datadog.mdx index 587516b1..8971cfde 100644 --- a/product/admin/mcp-server/datadog.mdx +++ b/product/admin/mcp-server/datadog.mdx @@ -126,7 +126,7 @@ Save your changes. C1 starts a sync that discovers the tools the Datadog server After you register the server, C1 runs tool discovery against Datadog. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification) for details. +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification) for details. Before anyone can call a Datadog tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to complete this setup. diff --git a/product/admin/mcp-server/freshdesk.mdx b/product/admin/mcp-server/freshdesk.mdx index bc8b0c79..b6146317 100644 --- a/product/admin/mcp-server/freshdesk.mdx +++ b/product/admin/mcp-server/freshdesk.mdx @@ -72,7 +72,7 @@ Save your changes. C1 starts a sync that discovers the tools the Freshdesk serve After you register the server, C1 runs tool discovery against Freshdesk. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Freshdesk tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/github.mdx b/product/admin/mcp-server/github.mdx index a943b92d..f1bc4cce 100644 --- a/product/admin/mcp-server/github.mdx +++ b/product/admin/mcp-server/github.mdx @@ -134,7 +134,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against GitHub. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a GitHub tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/gong.mdx b/product/admin/mcp-server/gong.mdx index db2b764b..dc68d35e 100644 --- a/product/admin/mcp-server/gong.mdx +++ b/product/admin/mcp-server/gong.mdx @@ -84,7 +84,7 @@ Save your changes. C1 starts a sync that discovers the tools the Gong server exp After you register the server, C1 runs tool discovery against Gong. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Gong tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/google-analytics-admin.mdx b/product/admin/mcp-server/google-analytics-admin.mdx index a078e1a1..548c3000 100644 --- a/product/admin/mcp-server/google-analytics-admin.mdx +++ b/product/admin/mcp-server/google-analytics-admin.mdx @@ -137,7 +137,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Google Analytics Admin. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Google Analytics Admin tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/google-analytics.mdx b/product/admin/mcp-server/google-analytics.mdx index fe8d1834..b1411a33 100644 --- a/product/admin/mcp-server/google-analytics.mdx +++ b/product/admin/mcp-server/google-analytics.mdx @@ -133,7 +133,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Google Analytics. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Google Analytics tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/google-drive.mdx b/product/admin/mcp-server/google-drive.mdx index 519e07f9..6baad64f 100644 --- a/product/admin/mcp-server/google-drive.mdx +++ b/product/admin/mcp-server/google-drive.mdx @@ -136,7 +136,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Google Drive. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Google Drive tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/hubspot.mdx b/product/admin/mcp-server/hubspot.mdx index a3e9c620..4ad84834 100644 --- a/product/admin/mcp-server/hubspot.mdx +++ b/product/admin/mcp-server/hubspot.mdx @@ -76,7 +76,7 @@ Save your changes. C1 starts a sync that discovers the tools the HubSpot server After you register the server, C1 runs tool discovery against HubSpot. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a HubSpot tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/jira-service-management.mdx b/product/admin/mcp-server/jira-service-management.mdx index ffe54330..25c9c080 100644 --- a/product/admin/mcp-server/jira-service-management.mdx +++ b/product/admin/mcp-server/jira-service-management.mdx @@ -85,7 +85,7 @@ Save your changes. The first time a user calls a Jira Service Management tool fr After you register the server, C1 runs tool discovery against Jira Service Management. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Jira Service Management tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/jira.mdx b/product/admin/mcp-server/jira.mdx index 1d442cb5..6a9f9d71 100644 --- a/product/admin/mcp-server/jira.mdx +++ b/product/admin/mcp-server/jira.mdx @@ -85,7 +85,7 @@ Save your changes. The first time a user calls a Jira tool from their AI client, After you register the server, C1 runs tool discovery against Jira. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Jira tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/linear.mdx b/product/admin/mcp-server/linear.mdx index b1ad3a0c..54ffa1d6 100644 --- a/product/admin/mcp-server/linear.mdx +++ b/product/admin/mcp-server/linear.mdx @@ -134,7 +134,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Linear. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Linear tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/linkedin.mdx b/product/admin/mcp-server/linkedin.mdx index 8f079919..ca73049c 100644 --- a/product/admin/mcp-server/linkedin.mdx +++ b/product/admin/mcp-server/linkedin.mdx @@ -79,7 +79,7 @@ Save your changes. The first time a user calls a LinkedIn tool from their AI cli After you register the server, C1 runs tool discovery against LinkedIn. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a LinkedIn tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/looker.mdx b/product/admin/mcp-server/looker.mdx index c768178d..a6a508b6 100644 --- a/product/admin/mcp-server/looker.mdx +++ b/product/admin/mcp-server/looker.mdx @@ -78,7 +78,7 @@ Save your changes. C1 starts a sync that discovers the tools the Looker server e After you register the server, C1 runs tool discovery against Looker. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Looker tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/lucid.mdx b/product/admin/mcp-server/lucid.mdx index a05a47ea..af92bb1f 100644 --- a/product/admin/mcp-server/lucid.mdx +++ b/product/admin/mcp-server/lucid.mdx @@ -127,7 +127,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Lucid. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Lucid tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/metabase.mdx b/product/admin/mcp-server/metabase.mdx index 35589585..7725782c 100644 --- a/product/admin/mcp-server/metabase.mdx +++ b/product/admin/mcp-server/metabase.mdx @@ -78,7 +78,7 @@ Save your changes. C1 starts a sync that discovers the tools the Metabase server After you register the server, C1 runs tool discovery against Metabase. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Metabase tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/metronome.mdx b/product/admin/mcp-server/metronome.mdx index 6ad42b7a..d2d3a80c 100644 --- a/product/admin/mcp-server/metronome.mdx +++ b/product/admin/mcp-server/metronome.mdx @@ -78,7 +78,7 @@ Save your changes. C1 starts a sync that discovers the tools the Metronome serve After you register the server, C1 runs tool discovery against Metronome. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Metronome tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/n8n.mdx b/product/admin/mcp-server/n8n.mdx index 82271220..a330e11e 100644 --- a/product/admin/mcp-server/n8n.mdx +++ b/product/admin/mcp-server/n8n.mdx @@ -79,7 +79,7 @@ Save your changes. C1 starts a sync that discovers the tools the n8n server expo After you register the server, C1 runs tool discovery against n8n. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an n8n tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/notion.mdx b/product/admin/mcp-server/notion.mdx index cc3ccbba..0d8133e8 100644 --- a/product/admin/mcp-server/notion.mdx +++ b/product/admin/mcp-server/notion.mdx @@ -140,7 +140,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Notion. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Notion tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/okta.mdx b/product/admin/mcp-server/okta.mdx index 14e83d30..68f3938d 100644 --- a/product/admin/mcp-server/okta.mdx +++ b/product/admin/mcp-server/okta.mdx @@ -88,7 +88,7 @@ Save your changes. With per-user OAuth, the first time a user calls an Okta tool After you register the server, C1 runs tool discovery against Okta. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an Okta tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/opsgenie.mdx b/product/admin/mcp-server/opsgenie.mdx index 9ce57529..9967c5ef 100644 --- a/product/admin/mcp-server/opsgenie.mdx +++ b/product/admin/mcp-server/opsgenie.mdx @@ -75,7 +75,7 @@ Save your changes. C1 starts a sync that discovers the tools the Opsgenie server After you register the server, C1 runs tool discovery against Opsgenie. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call an Opsgenie tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/pagerduty.mdx b/product/admin/mcp-server/pagerduty.mdx index 301a2809..53080c47 100644 --- a/product/admin/mcp-server/pagerduty.mdx +++ b/product/admin/mcp-server/pagerduty.mdx @@ -131,7 +131,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against PagerDuty. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a PagerDuty tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/ramp.mdx b/product/admin/mcp-server/ramp.mdx index 1bc5c7ec..dd666a45 100644 --- a/product/admin/mcp-server/ramp.mdx +++ b/product/admin/mcp-server/ramp.mdx @@ -100,7 +100,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Ramp. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Ramp tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/rapid7.mdx b/product/admin/mcp-server/rapid7.mdx index 7b399298..38754b14 100644 --- a/product/admin/mcp-server/rapid7.mdx +++ b/product/admin/mcp-server/rapid7.mdx @@ -79,7 +79,7 @@ Save your changes. C1 starts a sync that discovers the tools the Rapid7 server e After you register the server, C1 runs tool discovery against Rapid7. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Rapid7 tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/salesforce.mdx b/product/admin/mcp-server/salesforce.mdx index cde13cc3..6f62a05d 100644 --- a/product/admin/mcp-server/salesforce.mdx +++ b/product/admin/mcp-server/salesforce.mdx @@ -99,7 +99,7 @@ Save your changes. The first time a user calls a Salesforce tool from their AI c After you register the server, C1 runs tool discovery against Salesforce. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Salesforce tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/slack.mdx b/product/admin/mcp-server/slack.mdx index f65b469d..d518f1fb 100644 --- a/product/admin/mcp-server/slack.mdx +++ b/product/admin/mcp-server/slack.mdx @@ -82,7 +82,7 @@ Save your changes. The first time a user calls a Slack tool from their AI client After you register the server, C1 runs tool discovery against Slack. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Slack tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/statuspage.mdx b/product/admin/mcp-server/statuspage.mdx index a1c20419..d50967c8 100644 --- a/product/admin/mcp-server/statuspage.mdx +++ b/product/admin/mcp-server/statuspage.mdx @@ -75,7 +75,7 @@ Save your changes. C1 starts a sync that discovers the tools the Statuspage serv After you register the server, C1 runs tool discovery against Statuspage. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Statuspage tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/tableau.mdx b/product/admin/mcp-server/tableau.mdx index 31142446..a5ea47b0 100644 --- a/product/admin/mcp-server/tableau.mdx +++ b/product/admin/mcp-server/tableau.mdx @@ -110,7 +110,7 @@ Save your changes. C1 starts a sync that discovers the tools the Tableau server After you register the server, C1 runs tool discovery against Tableau. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Tableau tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/trello.mdx b/product/admin/mcp-server/trello.mdx index b32d5c45..51aee1f7 100644 --- a/product/admin/mcp-server/trello.mdx +++ b/product/admin/mcp-server/trello.mdx @@ -75,7 +75,7 @@ Save your changes. C1 starts a sync that discovers the tools the Trello server e After you register the server, C1 runs tool discovery against Trello. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Trello tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/vectara.mdx b/product/admin/mcp-server/vectara.mdx index 458b377d..411a77d8 100644 --- a/product/admin/mcp-server/vectara.mdx +++ b/product/admin/mcp-server/vectara.mdx @@ -127,7 +127,7 @@ For how shared and per-user credentials work across MCP servers, see [Configure After you register the server, C1 runs tool discovery against Vectara. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Vectara tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-server/wiz.mdx b/product/admin/mcp-server/wiz.mdx index 235d9169..d1a36028 100644 --- a/product/admin/mcp-server/wiz.mdx +++ b/product/admin/mcp-server/wiz.mdx @@ -80,7 +80,7 @@ Save your changes. C1 starts a sync that discovers the tools the Wiz server expo After you register the server, C1 runs tool discovery against Wiz. Discovered tools appear on the server's **Tools** tab. -Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **Settings** > **AI Connections**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). +Each tool starts as either **Pending review** or automatically **Approved**, depending on the option chosen when the server was set up or your tenant's default tool settings in **AI** > **MCP** > **Settings**. See [Require tool approval](/product/admin/enable-ai-access-management#require-tool-approval) and [Default tool classification](/product/admin/enable-ai-access-management#default-tool-classification). Before anyone can call a Wiz tool, it must be approved, added to a toolset, and bound to an access profile. Continue to [Govern tools and toolsets](/product/admin/tools-and-toolsets) to set this up. diff --git a/product/admin/mcp-servers.mdx b/product/admin/mcp-servers.mdx index f0ffba66..807019d5 100644 --- a/product/admin/mcp-servers.mdx +++ b/product/admin/mcp-servers.mdx @@ -23,7 +23,7 @@ This page walks through registering an MCP server with C1, linking it to a C1 ap -In C1, go to **Integrations > MCP servers**. +In C1, go to **AI > MCP**. Click **Add an MCP server**. @@ -42,7 +42,7 @@ Click **Register**. C1 connects to the server, validates it, and runs initial to -After registration, the server appears in **Integrations > MCP servers** with its discovered tools listed under the **Tools** tab and in the connected app's details page. You can sort the **Tools** tab by tool name, visibility, classification, state, and last updated. +After registration, the server appears in **AI > MCP** with its discovered tools listed under the **Tools** tab and in the connected app's details page. You can sort the **Tools** tab by tool name, visibility, classification, state, and last updated. ## Configure authentication diff --git a/product/admin/tool-call-hooks.mdx b/product/admin/tool-call-hooks.mdx index 9dfa93bf..f539a014 100644 --- a/product/admin/tool-call-hooks.mdx +++ b/product/admin/tool-call-hooks.mdx @@ -32,7 +32,7 @@ Every hook execution is recorded in the [audit log](/product/admin/audit-ai-tool -Go to **Settings > AI Governance** and open the **Hooks** tab. +Go to **AI > C1 Gateway > Settings** and find the **Hooks** section. Click **Add hook**. diff --git a/product/admin/tools-and-toolsets.mdx b/product/admin/tools-and-toolsets.mdx index 2b1bf43a..b03dfac3 100644 --- a/product/admin/tools-and-toolsets.mdx +++ b/product/admin/tools-and-toolsets.mdx @@ -21,7 +21,7 @@ Tools must be reviewed and approved before end users can request them. Use the s -In **Integrations > MCP servers**, open a registered server. +In **AI > MCP**, open a registered server. Click the **Tools** tab.