From b7725a3a37c23560e71b4f6434496488f5f72e70 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Wed, 22 Jul 2026 22:10:41 +0000
Subject: [PATCH 1/2] docs: note dashboard management for sandbox volumes

---
 sandboxes/overview.mdx | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/sandboxes/overview.mdx b/sandboxes/overview.mdx
index 5956ced..66e8240 100644
--- a/sandboxes/overview.mdx
+++ b/sandboxes/overview.mdx
@@ -92,6 +92,17 @@ Volumes provide persistent storage that can be mounted into sandboxes at launch.
 - [TypeScript Sandbox SDK volumes](/sandbox/sdk/typescript/volumes)
 - [Sandbox CLI volume commands](/sandboxes/cli#porter-sandbox-volume)
 
+### Manage volumes from the dashboard
+
+Every cluster with sandboxes enabled has a **Sandbox file storage** card in the **Add-ons** page. Open it to see:
+
+- **Overview** — the shared EFS disk backing sandbox volumes, with its created date and metered storage used.
+- **Volumes** — the cluster's volumes, with name, phase, attached sandboxes, and created date. Filter by name or phase, click a row to open the volume detail page, and delete idle volumes from there.
+
+Volumes attached to a running sandbox cannot be deleted; terminate the sandbox first, then delete the volume once it detaches.
+
+When you mount the `sandbox-volumes` disk into an app service, the dashboard shows a confirmation dialog reminding you that volume contents are written by sandboxed workloads and must be treated as untrusted input. See [accessing volume data from apps](/sandbox/sdk/python/volumes#access-volume-data-from-apps) for the full pattern.
+
 ## Next steps
 
 - [Sandboxes Getting Started](/sandboxes/getting-started)

From b10041f98d342415d05bf4a17fbc85cc2f40d9e4 Mon Sep 17 00:00:00 2001
From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com>
Date: Wed, 22 Jul 2026 22:14:28 +0000
Subject: [PATCH 2/2] docs: note sandbox-volumes is a reserved add-on name

---
 sandboxes/overview.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sandboxes/overview.mdx b/sandboxes/overview.mdx
index 66e8240..3adf6bb 100644
--- a/sandboxes/overview.mdx
+++ b/sandboxes/overview.mdx
@@ -94,7 +94,7 @@ Volumes provide persistent storage that can be mounted into sandboxes at launch.
 
 ### Manage volumes from the dashboard
 
-Every cluster with sandboxes enabled has a **Sandbox file storage** card in the **Add-ons** page. Open it to see:
+Every cluster with sandboxes enabled has a **Sandbox file storage** card in the **Add-ons** page, backed by a managed `sandbox-volumes` persistent-disk add-on that Porter creates and owns. The name is reserved — creating your own add-on named `sandbox-volumes` will fail with a validation error. Open the card to see:
 
 - **Overview** — the shared EFS disk backing sandbox volumes, with its created date and metered storage used.
 - **Volumes** — the cluster's volumes, with name, phase, attached sandboxes, and created date. Filter by name or phase, click a row to open the volume detail page, and delete idle volumes from there.