Overview
Open alerts
Fleet report
Top CPU consumers
Availability
Share of five-minute buckets that received a heartbeat in the selected window, worst first. A device is only judged on the time it existed in the window.
Operating systems
Agent versions
Agent rollout
Each device is compared with the newest agent version reported in this tenant.
Installed software
Counted from each device's newest inventory snapshot, most widely installed first.
Devices
Software
Upload an installer once, then deploy it to devices from here. The person at the device sees one approval dialog for the first install; after they approve, later installs are silent. Allowed types: .msi, .exe, .ps1, .bat, .cmd (up to 64 MiB).
Deployment history
The agent claims queued installs within about 10 seconds. History is kept for 7 days; every install is audited.
Installed software
Searches the newest inventory snapshot from each device. An empty search lists everything, newest snapshots only.
Alerts
Monitors
Notification targets
Each target receives the selected events as JSON, signed with HMAC-SHA256 in X-GoRMM-Signature when a secret is set. Secrets are stored but never shown again. The server-level webhook from the command line still fires too.
Maintenance windows
While a window is active, heartbeats are still recorded but monitors are not evaluated for the selected scope, so no alerts open or resolve.
Remote sessions
Every session needs approval from the user at the endpoint. Nothing runs before that approval.
Session
Runs on the endpoint only while the user-approved session is active. Output is capped at 64 KiB.
Files
Files are limited to 8 MiB. The endpoint must have an existing parent directory.
Screen
Captures run only in the approved session and are taken from the signed-in user's desktop.
Scripts
Saved commands run on an endpoint only inside a session the user has approved. There is no unattended mode.
Security
Change password
Changing your password signs out every other session.
Two-factor authentication
Checking…
Sessions
Sign out of this browser and every other active session.
Users
Tenant policy
Require every user in this tenant to set up two-factor authentication. Users without it can only reach the enrollment screen until they finish.
Active sessions
API keys
Long-lived keys for integrations, sent in the X-API-Key header. A key acts as its role but cannot change passwords, two-factor settings or sessions. The secret is shown once when the key is created.
Enrollment tokens
Create a separate link for each employee and device. Each link enrolls one device, expires after its lifetime, and can be revoked before use.