What's included
- Two channels per agent: the signed-in user's session for remote access, and an always-on System channel for servers with nobody logged in.
- One-off commands (CMD or PowerShell) or saved scripts, run as the user or elevated.
- Nothing gets lost to a bad connection — a command sent to an offline machine sits in the queue and delivers on reconnect.
- Full history of every command and every remote session, per machine, with who ran what and when.
- Chat with the person at the computer: you start the conversation from the app and a window opens on their screen to answer — they can reply, never start one. Both sides can send files and paste screenshots, within the size and file types you allow; a file from a conversation is never run on the computer.
- Replies reach you anywhere in the app — a counter and a notice open the conversation — and every conversation stays on the computer's page, with who started it, who answered and when.
- An Agent activity window on the computer, behind a password you set, shows what the agent has done and what is waiting: commands and scripts with their results, backups and their next run, and pending updates.
Remote access, under your rules
- One Remote access menu, everywhere. On the computer's page, on a ticket — at the top and next to its computer — in the client's list of computers and in the Actions and right-click menus of Computers: the SL App session, Remote Desktop through the agent, a Remote Desktop Connection file for inside the client's network, or TeamViewer. An entry that cannot work right now is greyed out with the reason.
- Remote Desktop through the agent. RDP through a tunnel of the computer's agent, which works from outside the client's network. On Windows, the SL App agent on your own computer (1.2.40 or newer) opens Remote Desktop straight away — no file to download, no black windows — and closes the tunnel when you close Remote Desktop. It only opens connections of the organizations it belongs to.
- The user is asked — unless you decide otherwise. The person at the computer is asked to allow the session. Can connect without asking for authorization and Can turn off session recording are two permissions of each user, off by default for everyone, administrators included; only an administrator can give them, each change is in the audit log, and the server checks both when each session starts.
- No ghost sessions. Closing a session's window ends it on the computer too, and a session nobody is watching any more ends on its own after two minutes. If someone is already connected to the computer, you see who and since when instead of a black screen, and their session carries on undisturbed.
Screen & commands
Full remote sessions under your consent rules, Remote Desktop through the agent, a chat with the person at the computer, and one-off commands queued and delivered automatically when an offline machine comes back.