---
title: "Augmentt Integration: Overview"
url: "https://help.psarev.io/en/article/augmentt-integration-overview"
language: "en"
last_updated: "2026-11-18T19:39:19.161Z"
---

# Augmentt Integration: Overview

Augmentt Secure is a security platform for Managed Service Providers that monitors their clients' Microsoft 365 tenants and raises alerts when something needs attention, such as a new admin without multi-factor authentication, a risky sign-in, or a mailbox rule change.

You can integrate Rev.io with Augmentt using the Integrations Library in the Admin module. The integration turns Augmentt security alerts into tickets in Rev.io, so your team can track and work them where you already run service. It does two things.

-   **Alert ticketing.** When Augmentt detects something, it sends the alert to Rev.io, and the integration creates a ticket for the right customer with the alert's details filled in. This happens in real time, with one ticket for each alert. See the [Augmentt Integration: Alert Ticketing](https://help.psarev.io/en/article/augmentt-integration-alert-ticketing) article for more information.
-   **Roster sync.** Once a day, the integration compares your Augmentt tenants to your Rev.io customers and suggests which tenant belongs to which customer. You confirm the matches, so alerts land on the correct customer. See the [Augmentt Integration: Roster Sync](https://help.psarev.io/en/article/augmentt-integration-roster-sync) article for more information.

The integration works one way, from Augmentt to Rev.io. It never changes alerts, tenants, or settings in Augmentt, and it never deletes anything in either system. The only customer it creates in Rev.io is a single catch-all customer named **Augmentt Default**, which holds alerts for tenants that aren't matched to a customer yet.

| **IMPORTANT:** An alert for a tenant that isn't matched to a Rev.io customer still becomes a ticket. It is filed under the **Augmentt Default** customer and marked Unmapped, so no alert is lost. A ticket on Augmentt Default means that tenant still needs to be matched. |
| --- |

The following table shows when data moves from Augmentt to Rev.io.

| **Event** | **When it shows up** |
| --- | --- |
| **You complete setup** | *The alert ticket type and the Augmentt Default customer are created if needed, and the first roster sync runs.* |
| **Augmentt raises an alert for an enabled tenant** | *A ticket is created in real time, within moments.* |
| **An alert arrives for an unmatched tenant** | *A ticket is created in real time under Augmentt Default, marked Unmapped.* |
| **An alert is below your minimum severity or on your excluded list** | *No ticket is created.* |
| **The same alert arrives again** | *No new ticket is created.* |
| **A new tenant is added in Augmentt** | *It is suggested for matching on the next nightly roster sync.* |
| **You confirm a tenant match** | *Future alerts for that tenant land on the matched customer.* |

Augmentt sends each alert once. It doesn't send updates, resolutions, or past alerts, so each ticket reflects the alert at the moment it was raised. If you remove the integration, ticket creation stops, and your tickets, tenant matches, and the Augmentt Default customer are kept.

To set up the Augmentt integration, see the following articles.

[Augmentt Integration: Prerequisites](https://help.psarev.io/en/article/augmentt-integration-prerequisites)  
[Augmentt Integration: Configuration](https://help.psarev.io/en/article/augmentt-integration-configuration)  
[Augmentt Integration: Frequently Asked Questions](https://help.psarev.io/en/article/augmentt-integration-frequently-asked-questions)
