diff --git a/docs/inspector/evals.mdx b/docs/inspector/evals.mdx
index d88ac50fd..822bde35d 100644
--- a/docs/inspector/evals.mdx
+++ b/docs/inspector/evals.mdx
@@ -297,9 +297,11 @@ Any completed chat session can be turned into a test case without rewriting it f
 
 **From the Playground** — Open the **Sessions** rail, hover a session, and click **Promote to test case**.
 
-**From the Swarms tab** — Open a completed run, click a session row to select it, then click **Promote to test case** above the session viewer. The session must belong to a completed run attempt; sessions from in-progress runs show an error in the dialog instead of blocking at submit.
+**From the Swarms tab** — Open a completed run, click a session row to select it, then click **Promote to test case** in the session detail pane. The session must belong to a completed run attempt; sessions from in-progress runs show an error in the dialog instead of blocking at submit.
 
-In both cases the dialog shows the servers recorded for that session, lets you set a case title and suite name, and (when attachment pickers are enabled) lets you configure the server attachment and client host for the new suite.
+**From User Testing** — Open a scenario's **Sessions** tab, select a session, and click **Promote to test case** in the session detail pane. Only project members can promote sessions; project guests can view sessions but the promote button is not shown to them.
+
+In all cases the dialog shows the servers recorded for that session, lets you set a case title and suite name, and (when attachment pickers are enabled) lets you configure the server attachment and client host for the new suite.
 
 ## Generating cases from your tools