> ## 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 DrayTek VigorACS integration brings to your Neo Agent setup

DrayTek VigorACS is the central management server your clients' Vigor routers, switches and access points report to. Connect your VigorACS to Neo once, at the MSP level, with its address and a VigorACS user. It works with a VigorACS you host yourself and with one a DrayTek distributor hosts for you.

## What Neo can do with VigorACS

> [card] A client's routers
>
> List the Vigor devices in a client's networks with their name, model and address, and find a device by its serial number or IP address.

> [card] Offline devices
>
> Read which of a client's devices VigorACS sees as offline, to answer an "internet down" ticket.

> [card] Router values
>
> Read a router's own TR-069 values live, such as its model, firmware, uptime, WAN address and connected LAN hosts.

> [card] Reboot and changes
>
> Reboot a device, change one TR-069 setting, enable, disable or move a device, and manage networks, provisioning profiles, user groups and users.

Some changes always ask a technician first, under every access profile, such as a factory reset or any change to VigorACS users: [the full list](https://docs.neoagent.io/integrations/draytek-vigoracs/connecting-to-neo.md#changes-that-always-ask-a-technician).

## Your clients' networks are mapped automatically

Neo matches each VigorACS network to a company in your PSA and keeps the mapping on the VigorACS card's **Organization Mapping** tab. It refreshes the mapping when you save the user, and again on each nightly PSA sync. A client can have several networks, such as one per site under the client's own network, so several networks can map to one company. The root network is never mapped.

Matching tries the network's name first, then the name of its parent network: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest.

**A name match, or one you confirm, is handed straight to your agents**, so they start from the client's networks without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. A mapping you set by hand survives every later sync.

On a ticket, an agent reaches only the networks mapped to the ticket's company, and only the devices on them: Neo checks that a device is on one of those networks before it reads or changes it.

## Credentials stay out of the agent's context

Neo removes passwords from every VigorACS answer before an agent sees it: the sign-in a network gives its devices, a user's password, and every TR-069 value whose name says it is a password or a Wi-Fi key.

## Next steps

> [card] [Connect DrayTek VigorACS](https://docs.neoagent.io/integrations/draytek-vigoracs/connecting-to-neo.md)
>
> Turn on VigorACS's REST API, create a user for Neo, and save it in Neo.


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