> ## 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 MPS Monitor to Neo

> Create an app in the MPS Monitor portal, save its Client ID and Client Secret with a portal user in Neo, and turn MPS Monitor on per agent

You connect MPS Monitor once at the MSP level. Neo signs in as one portal user of your dealer account and sees what that user sees.

## 1. Create the app and pick the user

**1. Create the app**

Sign in to the MPS Monitor portal, open the **developer** section, and create the app credentials. Copy the **Client ID** and the **Client Secret**.

**2. Pick the portal user**

Choose the portal user Neo signs in as: a dealer user whose role can see your customers and the areas your agents need. A user of its own for Neo keeps its actions apart in the portal's history. Two-factor sign-in on that user can stop Neo signing in with a password.

## 2. Add the credentials in Neo

**1. Open Integrations**

In the Neo Dashboard, open **Integrations** and find the MPS Monitor card, under Other.

**2. Save the credentials**

Enter the **Client ID**, the **Client Secret**, and the portal user's **User name** and **Password**, and click **Save**. Neo signs in to MPS Monitor with them before saving, so a wrong value is reported straight away.

Neo then lists your customers and maps them to your PSA companies on the **Organization Mapping** tab. If the user changes its password in the portal, save the new one on the card.

## 3. Turn MPS Monitor on per agent

Open the agent, go to the **Tools & Settings** tab, and configure the MPS Monitor block under **Tools & Integrations**. Pick a profile, or set each area:

| Area | Access levels you can pick | Notes |
| - | - | - |
| **Supply Alerts and Shipments** | Disabled, Read Only, Read/Write | Needed for supply alert reports and to record a shipment. Helpdesk runs it on its own. |
| **Devices and Counters** | Disabled, Read Only, Read/Write | Deleting a device always asks. Helpdesk asks before a device change. |
| **Device Management (HP SDS and Zebra)** | Disabled, Read Only, Read/Write | Removing a device from HP SDS or the cloud DCA always asks. |
| **Data Collectors** | Disabled, Read Only, Read/Write | Removing a data collector or cluster always asks. |
| **Alert Limits and Notifications** | Disabled, Read Only, Read/Write | |
| **Customers, Offices and Projects** | Disabled, Read Only, Read/Write | Deleting a customer always asks. |
| **Supply Catalog and Pricing** | Disabled, Read Only, Read/Write | |
| **Contracts and Invoices** | Disabled, Read Only, Read/Write | |
| **Users and Roles** | Disabled, Read Only, Read/Write | IT Admin asks a technician before a change. Removing a user's second factor always asks. |
| **Dealer Settings and Integrations** | Disabled, Read Only, Read/Write | IT Admin asks a technician before a change. |
| **Reports and Operation Logs** | Disabled, Read Only | |

See [MPS Monitor API](https://docs.neoagent.io/agents/tools/management/mps-monitor-api.md) for what the agent can do.

## Set up an agent

Ask your Neo Support Agent for the agent you need, for example: "Set up a scheduled agent that runs every weekday at 7:00. It lists the open MPS Monitor toner alerts that have no shipment yet, and opens a ticket for each alert under the customer's company, with the printer, the toner colour, its level, the forecast and the suggested part number. It does not open a second ticket for an alert that already has one."


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