Session flow

This guide follows the person-visible order of a resource session. Identity, scope, and assignment defines decision inputs; Session policies defines runtime controls.

Launch

1. The person signs in and opens Resources.
2. The panel lists assigned, visible resources.
3. The person selects an RDP, VNC, SSH, terminal, or Kubernetes work path.
4. The launch request is evaluated with the current access decision and resource readiness.
5. An open result starts the browser work surface.

A closed result keeps the work surface closed and shows a reason category: assignment, duration, readiness, active-session conflict, or policy.

During work

The browser surface carries the selected protocol. Duration, input, clipboard, file transfer, read-only view, and observation options follow the active session policy.

When a short connection interruption occurs, supported session types can enter their reconnect behavior. Work ends when resource state or policy produces closure.

Closure

The person can end the session, duration can expire, the connection can close, or an authorized role can terminate active work. Revocation and evidence covers closing both active work and future access.

Session summary

The session view shows start time, work duration, closure reason, and important session events. This summary supports operations and troubleshooting.