> ## 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

> What the ControlUp integration brings to your Neo Agent setup

ControlUp monitors your clients' virtual desktops and servers (Citrix, VMware Horizon, Azure Virtual Desktop, RDS) in real time, raises triggers that alert and run automations, and keeps the history. Connect your ControlUp organization to Neo once, at the MSP level, with an API key and your organization ID.

## What Neo can do with ControlUp

> [card] Alerts
>
> Read the trigger behind a ControlUp alert ticket, when it fired and on which machine, and note in the ticket what it means.

> [card] Statistics
>
> Read a machine's load now, logon times, session timelines, host metrics and the Windows events ControlUp keeps.

> [card] Machines
>
> Add a new server to monitoring, move one to another folder, or remove a retired one.

> [card] Mute and unmute
>
> Mute a machine's alerts for maintenance by moving it into your maintenance folder, and move it back after.

> [card] Triggers and automations
>
> Switch a trigger or automation off and on with a reason in ControlUp's audit log, or create one.

> [card] More ControlUp products
>
> With the access you choose, Neo also works with ControlUp for Desktops, Compliance, Synthetic Monitoring, Workflows, DaaS IQ and your users and roles.

## Your clients in ControlUp

You keep each client's machines in their own folders in ControlUp, so there is no Organization Mapping tab: Neo finds a machine by its name from the ticket and works in the folder it is in.

## Muting a machine

ControlUp mutes alerts by scope: a trigger fires for the folders it includes, minus the folders it excludes. Neo mutes a machine by moving it into your maintenance folder, a folder every trigger excludes, and notes on the ticket the folder it came from, so it can move it back. Create the folder once in the ControlUp console; Neo can exclude it from your triggers for you. To mute one alert for every machine, Neo switches that trigger off.

## What Neo never does

* Write an organization ID into a call: Neo puts the ID you saved there, so a call reaches only your organization.
* Download the RDP file of a DaaS IQ master image.
* Show the secrets an answer can carry: a Synthetic Monitoring Scout's MFA seed, a webhook's password or token, and Azure credentials. Neo removes them before an agent sees the answer.

## Next steps

> [card] [Connect ControlUp](https://docs.neoagent.io/integrations/controlup/connecting-to-neo.md)
>
> Create an API key and save it in Neo with your organization ID.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.