Notifications
ZestSSH collects the events it raises into one place: a notification center you reach from the bell in the app bar. Instead of a toast you might miss, every alert also lands in a history you can scroll back through, so you can see what happened while you were on another screen.
The bell and unread count
Section titled “The bell and unread count”The bell sits in the home app bar. When something needs your attention it shows an unread badge with a count. Tapping the bell opens the history; opening the history marks the current entries as seen, and the badge clears.
Whether an entry raises the badge depends on its severity.
Severity levels
Section titled “Severity levels”Every notification has one of four severities, which set its color, how long it stays on screen, and whether it counts as unread:
| Severity | Used for | Behavior |
|---|---|---|
| Info | Background events, for example “Tab closed” or “Identity saved” | Auto-dismisses quickly, does not raise the unread badge |
| Success | Something finished, for example “Connected to host” | Same as info, with the success accent color |
| Warning | Actionable but not fatal, for example “Host key changed” or “Password expires soon” | Kept in history, raises the unread count |
| Error | Something failed | Stays on screen until you dismiss it, raises the unread count |
History
Section titled “History”The history lists notifications newest first. It is kept locally and survives restarts, capped at the most recent 200 entries and 30 days, whichever comes first, so it never grows without bound.
In the history you can:
- Swipe an entry to dismiss it.
- Mark a group as read when related entries are grouped together.
- Tap an entry’s action, when it has one, to jump straight to what it refers to.
In-app toasts
Section titled “In-app toasts”As an event happens, ZestSSH also shows a brief toast so you get the alert immediately without opening the bell. Info and success toasts fade on their own; a warning stays in history; an error stays visible until you dismiss it.
System notifications
Section titled “System notifications”On Android and iOS, ZestSSH can also post notifications at the operating system level, so you are alerted even when the app is in the background. These cover:
- Transfers, so you know when a large upload or download finishes.
- Server monitor resource alerts, when a monitored host crosses a threshold you set.
- Sessions, for connection events worth surfacing.
System notifications need the operating system’s permission. The first time it is relevant, ZestSSH asks; if you decline, a banner offers to open your system settings so you can turn them back on later.
Settings
Section titled “Settings”Open Settings, Notifications to manage them. From there you can:
- Turn system notifications on or off per category: Transfers, Server Monitor, and Sessions.
- Open your device’s notification settings for ZestSSH directly, to change permission or per-channel behavior in the OS.
The in-app bell and history are always available; the settings control what is also delivered at the system level.
Platform availability
Section titled “Platform availability”| Platform | Notification center (bell, history, toasts) | System notifications |
|---|---|---|
| Android | Yes | Yes |
| iOS | Yes | Yes |
| Windows, macOS, Linux | Yes | Uses the in-app center |
Privacy
Section titled “Privacy”Notifications are generated on your device from events in your own session. The history is stored locally and is never sent to a server, and it is not part of cloud sync. Uninstalling the app clears it.