Skip to main content
You connect Cove once at the MSP level. One API user signs Neo in under your company in the Cove management console and reaches every customer below it.

​
1. Add an API user

1

Open Users

Sign in to the Cove management console at backup.management and open Users.
2

Add the user

Add a user for Neo, at your own company’s level, with an email address you control. Turn on API Authentication. Its role decides what Neo may read and change: a role that can only read keeps every agent read-only, whatever its permissions in Neo.
3

Note the sign-in details

Note the user’s email address and password, and your company’s name exactly as the console’s customer list shows it.
If the user’s password changes, or someone removes the user or turns API Authentication off, Neo cannot sign in until you save the new details here.

​
2. Add the user in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations and find the Cove Data Protection card, under Backup & Recovery.
2

Save the sign-in details

Enter the Customer Name, the API User Email and the API User Password, and click Save settings. Neo signs in to Cove before saving, so wrong details are rejected straight away.

​
3. Turn Cove on per agent

Open the agent, go to its Tools & Settings tab, click Backup & Recovery, and expand the Cove Data Protection block. Pick one of its Presets, or set each area yourself:

​
Start a backup through your RMM

The Backup Manager runs on each device, so Neo starts a backup by running a component in your RMM. Neo finds it in your script library by its name, so add these two to your RMM (Datto RMM: a PowerShell component, target Computer) with a name that says what each does, such as Cove - Restart Backup Service and Cove - Start Backup. Both commands come from N-able’s Backup Manager documentation.
Turn on Execute RMM Script for the agent. Your RMM’s own approval setting for scripts applies. Without these components, the agent tells the technician the command to run instead.

​
Use it on backup tickets

An agent that triggers on your backup tickets (Cove notifications, or an RMM monitor that says Backup Service Controller stopped) finds the device in Cove, reads why its last session failed and when it last succeeded, restarts the service or starts the backup through your RMM, and reads the next session. When the device also waits for a reboot (Datto RMM’s RebootRequired patch status), the agent notes it on the ticket and tells the technician, who picks the time. Map each customer on the Organization Mapping tab first: on a ticket, the agent reads only the customer mapped to the ticket’s company. See Cove Data Protection API for what the agent can read and change.