diff --git a/docs/run/sessions.mdx b/docs/run/sessions.mdx
index 8ea4d3b1d3..ca9b4c6df0 100644
--- a/docs/run/sessions.mdx
+++ b/docs/run/sessions.mdx
@@ -29,6 +29,10 @@ The basic workflow for sessions is as follows:
 3. The _interactive timeout_ runs between the jobs in a session. Every session has an interactive timeout value (ITTL, or interactive time to live). If there are no session jobs queued within the ITTL window, the session is temporarily deactivated and normal job selection resumes. A deactivated session can be resumed for the next job<sup>*</sup> if the session has not reached its maximum timeout value.
 3. If the maximum timeout value is reached, the sessions end and any remaining queued jobs fail.
 
+<video title="A line of users is shown. The one in the current session becomes larger than the rest and has rotating arrows around them, indicating that they are the priority. Boxes (jobs) are seen being sent to the QPU (represented by a chandelier) from the current user. Other users begin to pop up during the animation and their jobs appear beneath them as they wait for the prioritized user's session to end. A progress bar appears above the prioritized user to represent the interactive TTL. After the prioritized user's session finishes, the line moves ahead toward the system, and the next person's jobs can begin processing." class="max-w-auto h-auto" controls>
+  <source src="/videos/run/sessions/demo.mp4" type="video/mp4"></source>
+</video>
+
 <Admonition type="note">
 * The job must go through the normal queue to reactivate the session.
 </Admonition>
diff --git a/public/videos/run/sessions/demo.mp4 b/public/videos/run/sessions/demo.mp4
new file mode 100644
index 0000000000..27c4826e6a
Binary files /dev/null and b/public/videos/run/sessions/demo.mp4 differ