diff --git a/src/content/docs/ci-insights/runners.mdx b/src/content/docs/ci-insights/runners.mdx
index 2020086dfb..3f28f10d4f 100644
--- a/src/content/docs/ci-insights/runners.mdx
+++ b/src/content/docs/ci-insights/runners.mdx
@@ -3,6 +3,9 @@ title: Self-hosted runners
 description: Monitor the self-hosted CI runners behind your pipelines so you can spot capacity bottlenecks, degraded machines, and wasted spend.
 ---
 
+import { Image } from "astro:assets"
+import RunnersScreenshot from "../../images/ci-insights/runners.png"
+
 Self-hosted runners are the machines that execute your CI. Mergify doesn't provision
 or control them. It watches the jobs they run and turns that data into metrics about
 capacity, performance, cost, and reliability.
@@ -51,6 +54,8 @@ how each runner compares to its peers. Each runner carries a health status, so a
 underperforming or unstable one is easy to single out. You can also follow each
 runner's trends over time and see how heavily it is being used.
 
+<Image src={RunnersScreenshot} alt="Self-hosted runners fleet view" />
+
 ## No runner setup required
 
 Once CI Insights is enabled, Mergify tracks your runners automatically. It works out
diff --git a/src/content/docs/ci-insights/setup/github-actions.mdx b/src/content/docs/ci-insights/setup/github-actions.mdx
index c519e97af3..2205cda02d 100644
--- a/src/content/docs/ci-insights/setup/github-actions.mdx
+++ b/src/content/docs/ci-insights/setup/github-actions.mdx
@@ -4,6 +4,8 @@ description: Enable Mergify CI Insights and configure flaky test detection using
 ---
 
 import { Image } from "astro:assets"
+import TokenScreenshot from "../../../images/ci-insights/token.png"
+import GitHubSecretsScreenshot from "../../../images/ci-insights/gh-secrets.png"
 import JobsScreenshot from "../../../images/ci-insights/jobs.png"
 
 This page explains how to enable CI Insights for a repository using GitHub
@@ -22,6 +24,10 @@ Actions and how to configure repeated test executions for flaky test detection.
 
    This key will be used to upload test reports.
 
+   <Image src={TokenScreenshot} alt="CI Insights token in Mergify organization settings" />
+
+   <Image src={GitHubSecretsScreenshot} alt="Adding the MERGIFY_TOKEN secret in GitHub Actions" />
+
    :::tip
      If you use [Dependabot](/integrations/dependabot), you must also add
      `MERGIFY_TOKEN` to your **Dependabot secrets** (`Settings → Secrets and
diff --git a/src/content/images/ci-insights/auto-retry/rule.png b/src/content/images/ci-insights/auto-retry/rule.png
index 38fec386e2..79a4625531 100644
Binary files a/src/content/images/ci-insights/auto-retry/rule.png and b/src/content/images/ci-insights/auto-retry/rule.png differ
diff --git a/src/content/images/ci-insights/jobs.png b/src/content/images/ci-insights/jobs.png
index 1e661e1942..29e5ea0d31 100644
Binary files a/src/content/images/ci-insights/jobs.png and b/src/content/images/ci-insights/jobs.png differ
diff --git a/src/content/images/ci-insights/runners.png b/src/content/images/ci-insights/runners.png
new file mode 100644
index 0000000000..cf0301c064
Binary files /dev/null and b/src/content/images/ci-insights/runners.png differ