Skip to main content
You connect SaaS Alerts once at the MSP level. One partner API key covers every client in your SaaS Alerts account.

1. Copy the API key

1

Open the API settings

Sign in to SaaS Alerts as a partner admin and open Settings > API.
2

Copy the key

Under Manage API, click Show key and copy the key. Copy it before you leave the page.
Do not reset the key in SaaS Alerts after you connect it. A reset replaces the key, and Neo loses access until you save the new key here.

2. Add the key in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → SaaS Alerts, under Threat Detection & Intelligence.
2

Save the key

Paste the API key and click Save settings. Neo checks it against SaaS Alerts before saving, so a wrong key is rejected straight away.

3. Turn SaaS Alerts on per agent

Open the agent, go to its Tools & Settings tab, click Threat Detection & Intelligence, and expand the SaaS Alerts block. Pick a preset, or set each area: Under every profile, deleting a customer or an application connection, turning Respond off, and a Reset User Password or Setup User MFA action that the agent runs itself ask a technician. Each of those two actions sends a password or an MFA setup link by SMS to the numbers the agent puts in the request. Every other Respond action and every rule-trigger decision follows the approval setting of Respond Triggers and Actions. Approving a trigger runs the rule’s own actions, a password reset or MFA setup included, with the SMS numbers set in the rule. Turn approval on there to keep a technician on each one.

Example: investigate alert tickets

Give the agent that triages your SaaS Alerts tickets the Read Only profile and an instruction like this:
When a ticket is a SaaS Alerts alert, look up the event and the user’s recent activity in SaaS Alerts, judge whether it needs action, and write what you found in an internal note.
See SaaS Alerts API for what the agent can read and change.