> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Connect your ConnectWise ScreenConnect (Control) instance to Neo Agent for device context, remote command execution, and end-user messaging

## Setup Overview

Setting up the ConnectWise ScreenConnect integration involves two main steps:

<CardGroup cols={2}>
  <Card title="Creating an API Secret" icon="key" href="/integrations/rmm/screenconnect/creating-the-secret">
    Install the RESTful API Manager extension in ScreenConnect and copy its authentication secret.
  </Card>

  <Card title="Connecting to Neo Agent" icon="link" href="/integrations/rmm/screenconnect/connecting-to-neo">
    Configure the connection between your ScreenConnect instance and Neo Agent using your instance URL and the API secret.
  </Card>
</CardGroup>

## Prerequisites

Before starting the integration setup, ensure you have:

* **Admin Access**: An administrator account on your ScreenConnect instance with permission to install and configure extensions
* **Your instance URL**: e.g. `https://yourcompany.screenconnect.com`

<Info>
  ConnectWise ScreenConnect (also sold as **ConnectWise Control**) is a remote-support and access tool. Neo Agent talks to it through the **RESTful API Manager** extension — there is no separate REST API to enable, just the extension and its authentication secret.
</Info>

## What Neo Can Do with ScreenConnect

Neo Agent reads installed-agent (session) data and, where you allow it, runs commands and messages end users — gated by per-area permission groups you configure in Agent Settings.

<Warning>
  **API actions only — not interactive remote control.** Neo works through the RESTful API Manager: it queries devices, runs commands and Toolbox items, and messages end users programmatically. Neo does **not** start an interactive remote-control session — no screen viewing or takeover, no manual keyboard/mouse control, and it never "logs in" to drive the desktop by hand. A technician still does that from the ScreenConnect client.
</Warning>

<AccordionGroup>
  <Accordion title="Sessions & Devices">
    * **Session lookup** — find installed agents by name or filter, read session detail (operating system, last-contact time, online status, custom properties)
    * **Command output** — read the result of commands queued on a session
    * **Write** — create support sessions, rename sessions, update custom properties, add notes
  </Accordion>

  <Accordion title="Commands">
    * **Execute** — send a shell or PowerShell command to a session and read back the output

    <Warning>
      ScreenConnect commands run with the agent's privileges — **SYSTEM** on Windows, **root** elsewhere. Enable **Require approval** on the Commands group to gate every command behind a technician.
    </Warning>
  </Accordion>

  <Accordion title="Toolbox & Messaging">
    * **Toolbox** — run a pre-staged Toolbox item on the endpoint
    * **Messaging** — send a chat message to the logged-on end user
  </Accordion>
</AccordionGroup>

<Tip>
  Write access is opt-in per area. In Agent Settings → Permission Groups, set the relevant ScreenConnect groups to **Read & Write** to enable session writes, command execution, and messaging.
</Tip>

## Available Actions

| Category                | Actions                                                            | Status                 |
| ----------------------- | ------------------------------------------------------------------ | ---------------------- |
| **Sessions**            | Find sessions, read session detail and command output              | Available (read)       |
| **Sessions**            | Create sessions, rename, update custom properties, add notes       | Available (read/write) |
| **Commands**            | Send a shell/PowerShell command and read the output                | Available (read/write) |
| **Toolbox & Messaging** | Run a pre-staged Toolbox item, send a chat message to the end user | Available (read/write) |

<Info>
  Neo Agent uses the ScreenConnect RESTful API Manager. There is no script catalog — Neo sends the command text directly, so no scripts need to be pre-registered for command execution.
</Info>