Connections, folders, and sessions
A connection is a saved configuration record. A folder organizes records but does not create a session. A session is the live runtime created when a connection opens. Keeping those concepts separate makes clone, import, reconnect, and detached-window behavior easier to reason about.
The tree supports nested folders, tags, favorites, custom icons, ordering, and color cues. These are organizational attributes; they do not change transport security or protocol behavior.
Editor map
| Tab | Purpose |
|---|---|
| Basics | Connection/folder type, name, protocol, target, port, and primary credentials |
| Protocol | Protocol-specific subtabs such as authentication, display, security, Network Path, and advanced controls |
| Behavior | Focus policy, close/retry settings, and versioned lifecycle automation rules |
| Organize | Parent folder, tags, icon, color, favorite state, and ordering metadata |
| Notes | Human-readable description and operational context |
Folders intentionally hide connection-only tabs. Protocol subtabs change when the protocol or target operating system changes.
Search settings instead of hunting
The editor’s settings search indexes visible labels, help copy, option text, safe current values, and protocol-aware destinations. Selecting a result opens the owning top-level tab and, when applicable, the exact Protocol subtab.
Sensitive keys—passwords, tokens, private keys, passphrases, secrets, recovery codes, and similar values—are excluded from the search index. Search metadata should navigate to a control without copying secret material into searchable text.
Protocol subtabs
RDP groups connection identity, authentication, display/input, resources, security, Network Path, network transport, advanced settings, and recovery. SSH groups authentication, terminal overrides, Network Path, connection networking, and recovery.
The dedicated Network Paths page explains why routing is separate from ordinary TCP, gateway, and terminal settings.
Save and reopen contract
Stable references—not display names—should be persisted for reusable collections such as chains, profiles, VPN connections, and parent folders. The editor keeps an unavailable current ID visible as an orphan so a deleted dependency can be cleared or replaced instead of silently disappearing.
Before connecting a critical target:
- Save the connection.
- Reopen it and confirm the selected protocol, IDs, and overrides.
- Review any Network Path diagnostics.
- Connect and inspect the resulting session rather than assuming editor presence equals runtime support.
Connection-level safety
- Use per-connection trust exceptions sparingly; prefer the central trust policy.
- Keep descriptive notes free of credentials.
- Treat exported connection files as sensitive whenever credential inclusion is enabled.
- Use folders and tags for policy grouping, but do not treat them as access controls.
- Review behavior actions that can close sessions, run scripts, or manipulate windows.