docs/documentation/platform/pam/concepts/session-lifecycle.mdx
When you connect to an account through PAM, a session is created. The session tracks who connected, when, for how long, and what they did. Here's what happens at each stage.
An AI agent goes through the same stages, with the same checks and the same recording.
When you click Launch Session on an account from the Accounts page (or run the CLI command), PAM checks:
If everything checks out, the session is approved and you can connect.
An AI agent cannot be prompted, so it supplies its reason up front, and it cannot use an account that requires MFA yet.
Once approved, the connection is established through the Gateway:
For Web Access, this all happens in the browser. For CLI Access, the CLI starts a local proxy and you connect your preferred client to localhost.
While you're connected:
You can see your active sessions on the Sessions page.
A session ends when:
exit)Recordings are available in real-time — you can review activity even while the session is still active.
Every session is logged:
Admins and Auditors can review sessions from the Sessions page. See Session Recording for details on how recordings work.