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

# Connecting Bigleaf to Neo

> Create a Bigleaf Cloud Connect API token and save its key and password in Neo

You connect Bigleaf once at the MSP level. The token acts as the Cloud Connect user who creates it, and reaches every company and site that user can.

## 1. Create the API token

**1. Check that Token management is on**

Token management is off by default. If you do not see it in step 2, ask your company's Super Admin in Bigleaf, or Bigleaf Support, to turn it on for your user.

**2. Open User settings**

Sign in to the Bigleaf Cloud Connect dashboard as the user whose access you want Neo to have, and open **User settings**.

**3. Create a token**

Under **Token management**, click **New token**.

**4. Copy the key and the password**

Copy the token key and its password. The password shows only once; if you lose it, revoke the token and create a new one.

> [!NOTE]
>
> Bigleaf takes one token for all your clients, and no per-client key. For a client that licenses Bigleaf directly, ask the client to add your Cloud Connect user to its company, and its sites appear under your token.

> [!NOTE]
>
> Bigleaf tokens do not expire. If you remove the user from a company, or turn off their Token management, the token loses that access at once.

## 2. Add the token in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the Bigleaf card, under Networking.

**2. Save the key and password**

Paste the **Token Key** and the **Token Password** and click **Save settings**. Neo checks them against Bigleaf before saving, so a wrong pair is rejected straight away.

## 3. Turn Bigleaf on per agent

Open the agent, go to its **Tools & Settings** tab, click **Networking**, and expand the **Bigleaf** block. Pick the **Read Only** preset, or set each area yourself:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Site Status and Risks** | Disabled, Read Only | Each site's status, its circuits', routers' and switches' status, and the risks Bigleaf raised with their recommended action. |
| **Site Configuration** | Disabled, Read Only | Each site's circuits (type, ISP bandwidth, usage setting, WAN addressing), LAN networks, routers and points of presence. |
| **Companies and Users** | Disabled, Read Only | The Bigleaf companies and the Cloud Connect users the token reaches, with their emails. |

Bigleaf's API has no write, so no area offers Read / Write and nothing ever asks a technician.

## Use it on Bigleaf alert tickets

Bigleaf emails its alerts, such as "circuit down" and "Site Down", and they open tickets on the client's company. An agent on such a ticket finds the site the alert names among the client's mapped sites, reads whether the site or circuit is still down and since when, and which ISP circuit it is, so the technician knows whom to call. On a "Site Restored" alert it confirms the site is healthy now. Map each client's sites on the Organization Mapping tab first: on a ticket, the agent reads only the sites mapped to the ticket's company.

A chat or a scheduled agent with no ticket can read every site, for example to list the sites with a circuit down.

See [Bigleaf API](https://docs.neoagent.io/agents/tools/networking/bigleaf-api.md) for what the agent can read.


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