Connector Overview

Connectors are how Compass pulls live data from your IAM infrastructure. They're lightweight integrations that read metrics from your systems without modifying anything.

Architecture

Compass connectors follow the MCP (Model Context Protocol) standard. Each connector is a stateless service that:

1. Receives your platform credentials securely
2. Calls the platform's API to fetch metrics
3. Returns structured data to Compass for analysis
4. Discards credentials — nothing is stored in the connector layer

Read-Only Access

Connectors only read data. They never:

• Create, modify, or delete users
• Change access policies or permissions
• Write to audit logs
• Modify any configuration

You can safely grant read-only API access knowing Compass will not alter your environment.

Data Flow

Your IAM System → Connector → Compass AI → Report
     (source)     (fetches)   (analyses)   (output)

1. You provide API credentials in Compass settings
2. When a discovery runs, Compass sends credentials to the connector
3. The connector calls your IAM system's API
4. Raw metrics are returned to the AI for analysis
5. The AI generates findings based on the aggregated data

Connector Limits by Plan

Adding Multiple Connectors

You can connect multiple systems of the same type (e.g., two Azure AD tenants) or mix different platforms. More connectors give the AI a more complete picture of your IAM landscape, enabling cross-platform analysis like:

• Comparing identity counts across providers to detect orphan accounts
• Correlating provisioning times with ticket volumes
• Identifying privilege gaps between cloud and on-premises systems