diff --git a/public/docs-static/img/agent-network/connect-agent/agent-network-connect-agent-user-role.png b/public/docs-static/img/agent-network/connect-agent/agent-network-connect-agent-user-role.png
new file mode 100644
index 00000000..f758cdce
Binary files /dev/null and b/public/docs-static/img/agent-network/connect-agent/agent-network-connect-agent-user-role.png differ
diff --git a/src/pages/agent-network/connect-agents.mdx b/src/pages/agent-network/connect-agents.mdx
index a426f125..7bf93148 100644
--- a/src/pages/agent-network/connect-agents.mdx
+++ b/src/pages/agent-network/connect-agents.mdx
@@ -92,3 +92,17 @@ side: with nothing connected there is nothing for a policy to authorize. An admi
 starts by [connecting a provider](/agent-network/providers#connect-a-provider), then
 [creating a policy](/agent-network/policies) that covers the group the user belongs to. The
 page fills in as soon as both exist, no change is needed on the agent.
+
+## What a Regular User Sees
+
+A member with the plain **User** role gets the same page as an administrator: the same
+endpoint, the same per-tool snippets, and the providers their own policies allow. Only the
+sidebar differs, it carries **Connect Agent** and **Usage & Logs**, scoped to their own
+requests, without Providers, Policies, or Configuration.
+
+<p>
+    <img src="/docs-static/img/agent-network/connect-agent/agent-network-connect-agent-user-role.png" alt="Connect Agent page as seen by a member with the User role, whose sidebar carries only Connect Agent and Usage & Logs under Agent Network" className="imagewrapper-big" />
+</p>
+
+This is the page to point a new user at: nothing on it needs an administrator, and it always
+shows what that user in particular may call.