> ## 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.

# Overview

> What the SaaS Alerts integration brings to your Neo Agent setup

SaaS Alerts (by Kaseya) monitors your clients' Microsoft 365, Google Workspace and other SaaS accounts and raises security alerts. Connect your SaaS Alerts partner API key to Neo once, at the MSP level.

## What Neo can do with SaaS Alerts

<CardGroup cols={2}>
  <Card title="Alert tickets" icon="bell">
    Find the event behind a SaaS Alerts ticket from its Event ID, with its severity, IP, location and operation.
  </Card>

  <Card title="User activity" icon="list">
    Read the user's other events around the alert and how often the event type fires for the client.
  </Card>

  <Card title="Accounts and clients" icon="user-shield">
    Check whether the account is enabled and holds an admin role, and read the client's approved locations.
  </Card>

  <Card title="Suppressions and Respond" icon="shield-halved">
    Suppress a recurring event for one client, and run Respond actions on Microsoft 365 accounts when you allow it.
  </Card>
</CardGroup>

Every Respond action on an account, and every rule-trigger approve, reject or manual remediation, always asks a technician first.

## Your SaaS Alerts customers are mapped to clients

Neo matches each SaaS Alerts customer to a client in your PSA and keeps the mapping on the SaaS Alerts card's **Organization Mapping** tab, refreshed on each PSA metadata sync. With the mapping, an agent reads the alerts of the right client by its SaaS Alerts customer id.

Matching starts with the name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Then comes the domain of the customer's contact email, against the website on a PSA company. Neo skips a free-mail domain, a domain that two customers share, and your own domain. Last comes an AI match for the long tail.

A name match, or one you confirm, is handed straight to your agents. A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right client by hand. A mapping you set by hand survives every later sync.

## Next steps

<Card title="Connect SaaS Alerts" icon="plug" href="/integrations/saas-alerts/connecting-to-neo">
  Copy your partner API key from SaaS Alerts and save it in Neo.
</Card>


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