Baseline the behavior, not just the interface
We document what users may save, where configuration is expected to persist, how the endpoint is protected and what support should do when state is lost or corrupted. The baseline distinguishes a technical feature from an organizational control.
Decisions captured
| Area | Baseline question | Example outcome |
|---|---|---|
| Saved sessions | Which destinations may be bookmarked? | Named production and nonproduction folders |
| Passwords | May credentials be stored locally? | Restricted; approved vault workflow preferred |
| Master password | What protects stored client secrets? | Defined use plus recovery warning |
| Private keys | How are key files selected and protected? | Approved location and lifecycle owner |
| SSH browser | Which transfer method is acceptable? | SFTP by default; exceptions documented |
Recovery deserves equal attention
Official product guidance warns that resetting a master password removes previously saved connection passwords. User guidance therefore needs an approved recovery path that does not depend on retrieving locally saved secrets.
Support boundaries
The runbook separates client symptoms, endpoint issues, identity failures, network reachability and server-side authorization. This reduces trial-and-error changes that can obscure the original failure.