Browser Access Workspace

The browser workspace is the common entry point for users to open authorized assets. This page covers shared navigation; protocol-specific tools are documented separately.

Prerequisites

• The administrator created and successfully tested the asset.
• The current account has Resource Authorization.
• The Next Terminal server or gateway can reach the target.

Find and open an asset

Use the group tree and search field. The list contains resources authorized to the current account and available through the workspace. Click an asset to open it in a tab; multiple sessions can remain open in separate tabs.

Use by protocol

• SSH Assets: terminal, SFTP filesystem, snippets, monitoring and AI assistant.
• Windows / RDP Assets: desktop, clipboard, key combinations, network drive and RemoteApp.
• VNC and Telnet Assets: graphical VNC desktop or Telnet terminal.
• Web Assets: authenticated and authorized access to internal sites.
• Database Audit: database-client proxy access rather than a browser SQL session.

Session sharing

SSH, RDP and VNC sessions can provide a sharing entry. Verify the recipient and close sharing when collaboration ends. Shared activity remains subject to audit and data-access policies.

Files and clipboard

SSH file management directly operates the target SFTP filesystem. RDP uses Next Terminal storage and a Windows mapped drive. RDP/VNC clipboard availability depends on strategy and browser permission. See File Management.

Connection troubleshooting order

1. Confirm the asset still appears for the user.
2. Check authorization expiration and strategy.
3. Ask whether an administrator also fails; if so, inspect address, credential and gateway.
4. For RDP/VNC, consult Error Codes.
5. Review access and session logs.

For native clients, use the SSH Proxy Server, RDP Proxy Server or Termark.