Security & Backup

SaaS Alerts

Bring SaaS Alerts security events and monitored users into Dex so you can triage SaaS activity per customer in plain language.

Dex connects to the SaaS Alerts Reports API so admins can browse SaaS security activity conversationally - list and count security events by status, type, user, or time window, and review the monitored users for a customer. Read-only for now. SaaS Alerts ships as an MSP global app: one shared API key covers every monitored customer, and each Dex tenant is confined to a single customer by its roster id, so a scoped tenant sees only its own events and users.

Start free →

What Dex does with SaaS Alerts

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (Dex Pro)

List security events for a customer, filtered by alert status (low, medium, critical), event type, user, or time window
Count security events for a customer to size up activity at a given status or over a window
Review the monitored users recorded for a customer
List monitored customers from the MSP master connection
Deploy as an MSP global app - one shared API key, each Dex tenant confined to a single SaaS Alerts customer by its roster id

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Show me the critical SaaS Alerts events for this customer from the last 7 days
>How many security events were there at critical status this week?
>List the recent login.success events for jdoe@example.com
>Who are the monitored users for this customer?

Policy actions

Every action Dex can take on SaaS Alerts is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`saas_alerts_list_customers`	List monitored SaaS Alerts customers (MSP master connection only)	—
`saas_alerts_list_events`	List SaaS Alerts events for this customer (customerId forced)	self-only
`saas_alerts_count_events`	Count SaaS Alerts events for this customer (customerId forced)	self-only
`saas_alerts_list_users`	List monitored users for this SaaS Alerts customer (customerId forced)	self-only

How to configure SaaS Alerts

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In the SaaS Alerts management UI, go to Settings > API and generate an API key (Show Key).
2
In Dex, enable the SaaS Alerts integration and paste the API key - leave customer_id blank for the MSP master connection.
3
Dex validates the key with a live read before saving (the customer roster on the master).
4
Run discovery from the master to read each customer's roster id and map it to the matching Dex tenant.
5
Each scoped child tenant is confined to its customer id, which is forced on event and user reads.

Vendor documentation ↗

Credentials required

api_key: SaaS Alerts API key from the management UI (Settings > API > Show Key); sent as the api_key header and never echoed
customer_id: A child tenant's SaaS Alerts customer id (roster field id, e.g. 3s6hZNFny1P2AV0P1pzp); leave blank on the MSP master connection

Requirements

•A SaaS Alerts subscription with an API key from the management UI
•Read-only for now - Dex browses events, counts, and monitored users but does not modify them
•Deploy as an MSP global app: one shared API key on the master, each child tenant confined to a single customer by its roster id
•The customer roster is MSP-master only; scoped child tenants read only events, event counts, and users