ConnectWise ScreenConnect logo
Live

ConnectWise ScreenConnect

Who connected to what, when — your remote-access estate, answerable.

ScreenConnect is how your techs reach client machines. Connect it and a session can read the whole remote-access picture: every unattended machine, every session group, and the audit trail of who connected where.

The story

What changes once it’s connected.

Remote access is the most sensitive thing an MSP does, and the record of it usually lives buried in an admin page nobody opens until a client asks. With ScreenConnect on the board, that record is one question away — which machines are reachable, which techs connected to what this week, and what a given machine's access history actually looks like.

The connection is read-only by construction: the client has no write path. It never starts, joins, or transfers a remote session — it reads the estate and the audit trail, nothing else.

Things you can ask

Ask it like you’d ask a teammate.

>Which unattended machines haven't checked in this week?
>Who connected to the finance server at Family Worship Center this month?
>List every session group and how many machines are in each.
>Which machines is nobody ever remoting into — are we paying for access we don't use?
>Show the remote-access history for that server before yesterday's outage.
>Which techs used remote access this weekend, and where?

Skills included

Every skill, in the open.

4 skills across 4 areas

Read-only by construction — the client has no write path. It never starts, transfers, or changes a remote session; it only reads the estate and the audit trail.

Machines1The unattended-access inventory: every machine you can remote into, with its client, OS, logged-on user, and when it last checked in.
  • list_sessionsInventory every unattended-access machine — client, OS, agent version, logged-on user, idle time, last check-in.
Session groups1How the estate is organized — in practice, your client folders.
  • list_session_groupsList every session group and what's in it — your client-by-client folder structure.
Audit trail1The remote-access record: who connected to which machine, and when.⊘ Reads the audit log only — it cannot join, replay, or modify sessions.
  • query_audit_logAnswer 'who connected to what, when' — the remote-access audit, filterable by machine, tech, and time.
Agent & session1What this connection itself is and what it's allowed to do.
  • whoamiShow this connection's identity and scopes — what the session is allowed to read.

Connecting

Wire it in, in an afternoon.

How to connect

  1. 01Create a dedicated ScreenConnect user (a service login, not a person's).
  2. 02Give it the Administrator role — that grants the machine list and the access audit.
  3. 03Enter your ScreenConnect URL and that account's username and password here.
Vendor setup docs ↗

Patch your stack in.

Start the Switchboard free trial against your own environment — read-only, traced answers, live in an afternoon. The apps are on the shelf when you want them.

MSPStuff