Concepts
-
A workspace is where agents, sessions, and related resources live.
-
A client boundary (when enabled) separates customer or project scopes inside your org.
-
Roles and permissions control who can create agents, approve tickets, manage cloud VMs, and change policies.
Typical setup
-
Create a workspace for the team or engagement.
-
Attach or select a client if your org isolates work that way.
-
Invite members and assign roles that match their job (viewer vs operator vs admin patterns as shown in the portal).
-
Confirm members land in the intended workspace before sharing agent links.
Access problems
-
Wrong workspace selected in the portal header or switcher
-
Invite accepted under a different email than expected
-
Role too narrow to start agents or open VNC / Web IDE
Ask an org admin to adjust membership. Do not share personal login credentials to bypass permissions.