Skip to main content
Datto EDR and Datto AV (formerly Infocyte) protect your clients’ devices from one console: Datto AV quarantines malicious files, and Datto EDR raises alerts and responds on the device. Connect your Datto EDR console to Neo once, at the MSP level. One API token covers both products.

What Neo can do with Datto EDR

  • Investigate a Datto AV quarantine or a Datto EDR alert ticket: find the alert, read the quarantined file, its reputation and the device, judge whether it is a false positive, and write what it found in an internal note.
  • Find the alert from any of the ticket shapes: Datto EDR’s own Autotask ticket, a Datto RMM alert ticket (the path for Halo and ConnectWise), or an alert email.
  • List new quarantines on a schedule, so Low and Medium detections that never become a ticket are still reviewed.
  • Archive (acknowledge) and comment on alerts, scan devices, and manage devices, organizations and locations.
  • Restore or delete a quarantined file, isolate a device, run a response, and change exclusions and policies. You choose, per permission group, whether each of these asks a technician first.
The agent tool and its safety controls: Datto EDR API.

Your organizations are mapped to clients

Neo matches each Datto EDR organization to a client in your PSA and keeps the mapping on the Datto EDR card’s Organization Mapping tab, refreshed on each PSA metadata sync. With the mapping, a scheduled agent or a Chat Agent reads the alerts and quarantined files of the right client by its Datto EDR organization id. A token for an External Analyst sees only the organizations assigned to that user, so only those are mapped. On Autotask, matching starts with Datto EDR’s own Autotask integration, if you use it: when every location of an organization that you mapped to an Autotask account in Datto EDR points to the same account, that account is an exact match. Then comes the name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the long tail.

Organizations used as policy groups

Some MSPs use Datto EDR organizations as policy tiers, such as “Gold Tier”, and keep each client in a location under them. If you do, turn on Map locations on the Datto EDR integration’s Settings tab. It is off by default, and it applies on the next nightly sync. Leave it off if your organizations are your clients: a location named like a client would narrow that client to one location. With Map locations on, when an organization matches no client by its Autotask mapping or its name, Neo matches each of its locations the same way: Datto EDR’s own Autotask account mapping for that location, then the name (also the part before a dash, so “Contoso - Head Office” matches Contoso), then AI. A location shows on the Organization Mapping tab as its own row, for example “Gold Tier / Contoso”, and your agents read that client’s alerts and devices by its location id. Once one of its locations is mapped, the tier organization leaves the Organization Mapping tab, so it can never be mapped to one client by mistake. An organization that matches a client keeps that mapping, and its locations are not mapped one by one. An Autotask match, a name match, or one you confirm, is handed straight to your agents. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync.

Next steps

Connect Datto EDR

Create an API token in Datto EDR and save it in Neo with your console address.