Skip to main content
Audience: MSP staff with integration-management access and authorized credentials for the intended provider account. Open Settings > Integrations, find Cove Data Protection, and open its setup or configuration. If several connections exist, select the intended instance.

​
Prepare the provider account

In Cove, open Management > Users > API Users, choose Add API user, select the appropriate customer account, enter a requested login name and select an appropriate role. Choose Save and continue and securely save the token; it is displayed only once. See N-able’s API user instructions. Use an API user with access to the partners and backup information you need. A console sign-in account and an API user are different. Do not assume an account created under one client can see all sibling clients.

​
Connect

Blank Cove API Token field and its explanation in MSPortal setup.
The screenshot shows a blank MSP setup field, with no saved credential. The wizard has Connect and Map steps.
  1. Enter the credentials for the intended provider account.
  2. Choose Test Connection and resolve any reported error.
  3. For a new connection, choose Create Integration after the test succeeds.
  4. Continue to Map once the integration has been created.
Changing a new connection’s fields requires another test. Testing is separate from saving. For an existing connection, use Retest Connection when you need a current check; the saved verified state on opening the page is not a newly completed test. On Map, use Sync to request the partner list if it is empty or stale. Creating the connection does not itself prove that partner or backup data has been imported.

​
Map partners to companies

  1. Review the synchronized partner list. Use Sync if expected records are missing or stale, then wait for the result and refresh the list.
  2. Choose the correct MSPortal company for each intended partner, or use Quick Match and review the proposals.
  3. If a company does not exist, use the creation option carefully. Confirming creation creates the MSPortal company immediately; closing the wizard will not remove it.
  4. Review pending mappings and save them using the mapping screen’s save action or Complete Setup.
  5. Reopen the configuration and verify the saved company links. Check the destination company’s backup information after synchronization finishes.
Choosing a company stages a link. Removing an already saved link persists immediately; clearing a pending suggestion only clears the draft. Complete Setup saves pending mappings and requests background data synchronization. Its success message does not certify that the background job completed or that every backup is healthy. Map the actual organization, not just a similar name. Mapping associates provider data with an MSPortal company; it does not create a provider customer or run a backup job.

​
Troubleshoot missing data

  • Connection test fails: check the account scope and exact credentials. Confirm Partner Name matches the account under which the API user was created.
  • Expected partner is absent: confirm the API account can access it, request a list sync and inspect the result. Repeated company creation will not fix provider visibility.
  • Data appears under the wrong company: review the saved mapping for the correct connection before changing it.
  • Setup finished but data is absent: verify a saved company link and successful background sync. Allow the current job to finish before repeatedly requesting another.
  • Credential replacement: the existing Connect form’s retest is not a credential-update save action. Arrange the supported replacement with your administrator or MSPortal support before disabling the working credential.

​
Frequently asked questions

No. For a new connection, wait for a successful test, then choose Create Integration. That action saves the connection; synchronization is separate.
An existing integration can open with its saved verified state. Use Retest Connection when you need a current connection check, then inspect the result.
Do not treat a successful retest as a saved credential change. The existing connection’s Connect step does not offer a credential-update save action. Ask your MSPortal administrator or support for the supported replacement process before revoking the working credential.
Quick Match proposes links for review. Creating a missing company is a separate action that creates the company immediately; its provider link can still be pending. Review and save only the intended mappings.
Completion saves pending mappings and requests background synchronization. Check the correct connection, saved company mappings, provider access and sync result. A setup-success message is not evidence that backup data has finished loading.
No. Removing a saved link persists immediately. Clearing an unsaved suggestion only removes that pending suggestion. Verify the company and provider record before unlinking.