Profiles are connection recipes
A profile stores the details you choose: a display name, address, port, username and authentication selection. Groups and tags help distinguish machines with similar names. A profile is not a running session and does not grant access by itself. The server still checks authentication when you connect.
Groups are organizational aids, not automatically security boundaries or team permission rules.
Add and organize a server
- Choose Add a server and enter its connection details.
- Give it a distinctive name, such as Development database rather than only Database.
- Open Advanced settings to add groups, tags or supported per-host preferences.
- Check authentication and routing before saving.
- Reopen the profile and verify the destination before your first production action.
Use separate profiles when the same address requires different accounts or materially different routes. Do not assume changing a saved profile changes the connection already open in another tab.
Keep secrets in the right place
Saving a host does not necessarily save its password. Reusable credentials belong in the vault, not in names, tags, snippets or notes.
Cloud inventory, local profiles and enrolled local vaults have different storage behavior. Signing in does not automatically upload every local server. Review cloud and offline data before changing modes.
For a local profile backup, use Local Vault Sync and recovery. A host list alone is not proof that every private key or device-bound credential can be restored.