Integrations update

docs/Data-insights/Features/Integrations/Chat/opspilot-mcp.md

@@ -0,0 +1,93 @@
+# OpsPilot MCP
+
+Let AI assistants query OpsPilot over the Model Context Protocol (MCP).
+
+OpsPilot MCP brings OpsPilot to where your team already works. An AI assistant there can work with your telemetry and situations the way the OpsPilot coworker does, so you can ask without switching tools.
+
+Navigate to **Integrations** from the left-hand sidebar, then select **OpsPilot MCP**.
+
+---
+
+## What assistants can do
+
+Once connected, an assistant can read your **dashboards**, **metrics**, **logs**, **traces**, and the **situations** your coworker is tracking - and, depending on the permission tier, act on them.
+
+Each person connects their own assistant and signs in as themselves, so there is no key to paste and everyone sees what they can already see in OpsPilot.
+
+OpsPilot MCP declares no **capabilities**, so it provisions no dashboards or alerts of its own. It reads and acts on what is already in your account.
+
+---
+
+## Permission tiers
+
+| Tier | Description |
+|---|---|
+| **Read + Act** | The default. Assistants may read and act on what they find. Requires nothing - your plan grants it |
+| **Read-only** | Assistants may only read. Requires nothing, and holds the whole organisation to reading |
+
+The tier set on the install is the **ceiling for the whole organisation**, whichever address a person connects with. Read-only is enforced by OpsPilot rather than trusted to the client, so an assistant on a read-only connection is never offered the tools that change anything.
+
+---
+
+## Installing
+
+Click **Install** on the **OpsPilot MCP** card in the [integration catalog](../../integrations.md), or from its detail view. The dialog confirms which account the install will serve. Click **Install** to confirm.
+
+Installing makes OpsPilot available. Each person still points their own assistant at it.
+
+---
+
+## Connect your assistant
+
+Open **Connect** on the integration. Choose the address you want, then send it to your client or copy it.
+
+### Which address
+
+| Address | What it gives |
+|---|---|
+| **Full access** | The default. Read and act |
+| **Read-only** | Never offers the tools that change anything |
+
+The choice applies to the **connection**, not the account - so somebody who also adds the full address gets the full surface. To hold everyone to reading whatever they connect with, set the install's permission tier to **Read-only**. Where both apply, the stricter wins.
+
+### Sending it to your client
+
+**Connect** offers a button per client:
+
+| Client | How |
+|---|---|
+| **VS Code** and **VS Code Insiders** | Click the button to hand the address straight to the editor |
+| **Claude Code** | Copy the `claude mcp add` command and run it |
+| **Claude desktop and web** | Click **Open**, or copy the address and add it under **Customize → Connectors → Add custom connector** |
+
+!!! note "The address lives on the Connect page"
+    OpsPilot runs in more than one environment, so a written-down address names only one of them. Always take the address from **Connect** rather than copying one from documentation.
+
+---
+
+## Setting it up for everyone
+
+If you are an **Owner** of a Claude Team or Enterprise organisation, add it once for everybody: **Organization settings** → **Connectors** → **Add**, and paste the address from **Connect**.
+
+That covers desktop, web, mobile and Claude Code together. It makes OpsPilot available; each person still enables it and signs in as themselves.
+
+---
+
+## Check it works
+
+Ask your assistant:
+
+> *what situations are active right now?*
+
+A list means you are connected.
+
+---
+
+## Troubleshooting
+
+**A VS Code button does nothing.** Those buttons hand the address to the editor through a link the operating system routes, so nothing happens when that editor is not installed on the machine you are reading this on. Copy the address instead and add it from inside the client.
+
+---
+
+!!! question "Need more help?"
+    Contact support in the chat bubble and let us know how we can assist.

docs/Data-insights/Features/Integrations/Chat/slack.md

@@ -1,25 +1,110 @@
 # Slack Integration
 
-Connect OpsPilot to Slack to receive alert notifications and incident updates directly in your Slack channels.
+Talk to OpsPilot from Slack - mention it in a channel or DM it directly.
+
+The Slack integration brings OpsPilot to where your team already talks. Invite the bot to a channel and switch posting on, and the alerts, situations, and digests the coworker surfaces land there as they happen. Mention it there or message it directly and you get the same coworker you use in the app, so you can ask about what it just posted without switching tools.
+
+DMs are personal: each person links their own account.
 
 Navigate to **Integrations** from the left-hand sidebar, then select **Slack**.
 
 ---
 
-## Setup
+## Permission tiers
+
+| Tier | Description |
+|---|---|
+| **Read-only** | The default. Requires nothing to supply - it is granted with your plan. OpsPilot answers questions in Slack from what the organisation can already see |
+| **Read + Act** | Requires Read, plus a plan that includes assistant actions. Lets Slack users act on the organisation's behalf - acknowledging alerts, silencing, and triggering runbooks - subject to their own account link |
+
+---
+
+## Connecting your workspace
 
 1. In OpsPilot, go to **Integrations** and click **Slack**.
-2. Click **Connect** and follow the OAuth flow to authorise OpsPilot in your Slack workspace.
-3. Select the default channel you want notifications sent to.
-4. Click **Save**.
+2. Click **Add to Slack**. A Slack window opens asking you to sign in to your workspace.
+3. Enter your workspace's Slack URL (for example, `your-workspace.slack.com`) and click **Continue**. If you don't know it, use **Find your workspaces**.
+4. Sign in to the workspace. The method depends on how your workspace is configured - many require a Google account or another single sign-on provider on your organisation's domain.
+5. On the **Allow the "OpsPilot" app to access Slack** screen, choose the **Workspace** to install into, review the permissions OpsPilot is asking for, and click **Allow**.
+
+!!! note "Permissions OpsPilot requests"
+    Slack asks you to approve what OpsPilot can do in your workspace:
+
+    | | Permission |
+    |---|---|
+    | **View** | Content and info about channels and conversations |
+    | **View** | Content and info about your workspace |
+    | **Act** | Perform actions in channels and conversations |
+
+    Expand **More permissions** to see the full list, or click **Manage permissions** to change them. Slack shares the permissions you grant with OpsPilot.
+
+---
+
+## Inviting OpsPilot to a channel
+
+Connecting the workspace posts nothing anywhere. OpsPilot waits to be invited, so you choose which channels it appears in.
+
+In the channel you want situations in, run:
+
+```
+/invite @OpsPilot
+```
+
+OpsPilot introduces itself and waits. Situation posting is off until someone turns it on - tap **Enable situation posting** on the welcome card, or run:
+
+```
+/opspilot unmute
+```
+
+Situations at **warning** severity or above then land in that channel.
+
+---
+
+## Connecting your own account
+
+Direct messages are personal, so each person links their OpsPilot account once before DMing the bot. Message it and it hands you the link.
+
+Channel mentions need no linking - only DMs.
+
+---
+
+## What OpsPilot reads
+
+OpsPilot only reads messages that mention it. Background reading is off in every channel until someone turns it on:
+
+```
+/opspilot listen passive
+```
+
+`/opspilot status` shows where a channel stands, and `/opspilot listen off` stops it again.
+
+---
+
+## Checking it works
+
+In a channel OpsPilot is in, ask *"what situations are active right now?"*. An answer means the workspace is connected and the bot can reach your data.
+
+---
+
+## Slash commands
+
+| Command | Description |
+|---|---|
+| `/invite @OpsPilot` | Add OpsPilot to the channel |
+| `/opspilot unmute` | Turn situation posting on for the channel |
+| `/opspilot mute` | Stop the posts again, without removing the bot |
+| `/opspilot route` | Narrow what is posted by service, severity, or category |
+| `/opspilot listen passive` | Turn on background reading of the channel |
+| `/opspilot listen off` | Turn background reading off again |
+| `/opspilot status` | Show where the channel stands |
 
 ---
 
-## Using Slack with Alerts
+## Using Slack with alerts
 
-Once connected, you can select Slack as a contact point when configuring alert notification policies.
+You can also select Slack as a contact point when configuring alert notification policies.
 
-Navigate to **Alerts > Contact Points** and choose Slack as the delivery method. You can specify a channel per contact point to route different alerts to different channels.
+Navigate to **Alerting > Notifications**, open the **Contact Points** tab, and choose Slack as the integration type. See [Contact Points](../../New-alerting/contact-points.md) for the full setup.
 
 ---
 

docs/Data-insights/Features/Integrations/Cloud/aws.md

@@ -0,0 +1,65 @@
+# AWS
+
+Connect AWS for EC2, RDS, and other CloudWatch-held metrics.
+
+The AWS integration puts your AWS account's own monitoring data next to everything else you watch. CloudWatch metrics and logs arrive with dashboards for the services you are already paying for, so you can see how an account is behaving without building the views yourself or leaving to go and look.
+
+Navigate to **Integrations** from the left-hand sidebar, then select **AWS**.
+
+---
+
+## Permission tiers
+
+Unlike most integrations, AWS needs credentials you supply - an IAM role or key with the right CloudWatch permissions.
+
+| Tier | Requires |
+|---|---|
+| **Read-only** | The default. An AWS IAM role or key with `CloudWatch:Get*`, `List*`, and `Describe*` permissions |
+| **Read + Write** | The Read permissions, plus `CloudWatch:PutMetricAlarm` and related write actions |
+
+---
+
+## What it provisions
+
+AWS declares four capabilities - **Data Sources**, **Dashboards**, **Recording Rules**, and **Alerts**. The dashboards, alert rules, and recording rules are provisioned as soon as the install succeeds.
+
+The current version installs **16 dashboards**, covering the services CloudWatch reports on.
+
+---
+
+## Working across regions
+
+The dashboards follow the region configured on the installation. If you connect several AWS regions, install the AWS integration **once per region** - each instance gets its own data source, its own dashboards, and its own folder.
+
+Two dashboards are the exception, because AWS only reports their metrics to `us-east-1`. Both pin that region themselves, so they work whatever region an installation uses.
+
+---
+
+## Two dashboards need extra setup
+
+Two of the sixteen dashboards read metrics that AWS does not publish by default.
+
+### AWS Billing
+
+The **AWS Billing** dashboard reads `EstimatedCharges` from the `AWS/Billing` namespace. AWS publishes that metric only if billing alerts are switched on, and only into `us-east-1`. The dashboard queries that region regardless of the region you configured, so no change to the installation is needed.
+
+To switch it on, in the AWS console:
+
+1. Sign in to the **management account** of your organisation. The metric is published for the payer account, not for member accounts.
+2. Open **Billing and Cost Management** → **Billing preferences**.
+3. Enable **Receive CloudWatch billing alerts**, and save.
+
+!!! note
+    The metric starts being published from that point on and is not backfilled. The dashboard stays empty for the first few hours, and shows no history from before you enabled it.
+
+### AWS CloudFront
+
+CloudFront reports its metrics only to `us-east-1` as well. The dashboard pins that region itself, so it works whatever region the installation uses - but the credentials you supplied must be allowed to read CloudWatch in `us-east-1`.
+
+!!! warning
+    An IAM policy scoped to a single region will refuse this. If your CloudFront dashboard is empty, check that the credentials can read CloudWatch in `us-east-1`.
+
+---
+
+!!! question "Need more help?"
+    Contact support in the chat bubble and let us know how we can assist.

docs/Data-insights/Features/Integrations/Data/opentrace.md

@@ -0,0 +1,46 @@
+# OpenTrace
+
+Connect OpenTrace so OpsPilot can read your code alongside your telemetry.
+
+OpsPilot knows what your systems are doing. OpenTrace knows what your code is: what calls what, who owns a file, and what changed in which pull request. Connect your OpenTrace account and OpsPilot can use both when it answers you, so a question about a service that started erroring can reach the change that touched it.
+
+Navigate to **Integrations** from the left-hand sidebar, then select **OpenTrace**.
+
+---
+
+## What it adds
+
+With OpenTrace connected, OpsPilot can draw on your code as well as your telemetry when it answers you:
+
+- **What calls what** - the relationships between your services and components
+- **Who owns a file** - who to ask, or who to tell
+- **What changed in which pull request** - the change history behind the code
+
+That means a question about a service that has started erroring can reach the change that touched it, rather than stopping at the symptom.
+
+---
+
+## Your own account
+
+You connect your own OpenTrace account, and OpsPilot uses it only in **your** conversations. Each person connects their own account - it isn't shared across the organisation.
+
+Connect yours from **Integrations** → **User MCPs**, where OpenTrace appears under **Data** with a **Connect** button. The agent uses that connection only in chat, never in scheduled work and never on anyone else's behalf.
+
+---
+
+## Permission tiers
+
+OpenTrace runs **Read-only**, which is the default and the only tier. It requires nothing to enable.
+
+OpenTrace declares no **capabilities**, so it doesn't provision dashboards or alerts of its own - it adds context to the answers OpsPilot gives you.
+
+---
+
+## Installing
+
+Click **Install** on the **OpenTrace** card in the [integration catalog](../../integrations.md), or from the integration's detail view. The install dialog confirms which account the install will serve and shows the permission tier. Click **Install** to confirm.
+
+---
+
+!!! question "Need more help?"
+    Contact support in the chat bubble and let us know how we can assist.