1. Create the API token
A Slide API token belongs to the user who creates it and has that user’s role and permissions. Create it as a user whose role can do what your agents do: Slide’s Read Only role for agents that only read, or a role such as Business Continuity Technician for agents that resolve alerts and start backups. A dedicated Slide user for Neo keeps its actions apart in Slide’s audit log.1
Open API Tokens
Sign in to the Slide Console at console.slide.tech as that user and open My Settings > API Tokens.
2
Create the token
Create a token, name it Neo, and copy it.
2. Add the token in Neo
1
Open Integrations
In the Neo Dashboard, open Integrations and find the Slide card, under Backup & Recovery.
2
Save the token
Paste the API token and click Save settings. Neo checks it against Slide before saving, so a wrong token, or one whose user cannot read clients, is rejected straight away.
3. Turn Slide on per agent
Open the agent, go to its Tools & Settings tab, click Backup & Recovery, and expand the Slide block. Pick one of its Presets, or set each area yourself:
Deleting a client, powering off a Slide Box and pausing a system’s backups or alerts with no end always ask a technician, whatever the preset.
Use it on alert tickets
Slide sends its alert emails to the addresses on its Alert Email List (Account Settings in the Slide Console), which is how most MSPs open Slide tickets in their PSA. The titles name the system or box, for example[SRV-01] Backup failed: Failed to create VSS snapshot set or [Acme Dental] Slide Box storage is low (< 20% free), and each email links to its alert. An agent that triggers on those tickets reads the alert, checks the backups and verifications since, and resolves the alert once the system has recovered.
Map each client on the Organization Mapping tab first, and make sure your PSA files each Slide ticket under the customer’s company: on a ticket, the agent reads only the client mapped to the ticket’s company.
See Slide API for what the agent can read and change.