Source: qdash /integrations - c61 active-state stat card treatment, 2026-08-13

Each capability is a section with a heavy rule. Active connections are promoted to bordered stat cards that prove data is flowing; everything else waits as a quiet add row. View all expands the catalog in place.

Sources & enrichment

Bring identity and ownership context into qdash.

Okta active

1,204users matched86groups

config

Microsoft Entra IDMatch observed agents and users to Entra identities.

Request a source

Security & observability

Investigate qdash activity alongside your SIEM and observability stack.

Splunk active

278kevents12.3kfindings

config

DatadogSend findings and agent events

Microsoft SentinelSend findings and agent events

View All (6) Request an integration

Notifications & response

Alert teams or open incidents where people already respond.

Slack active

142notifications38high findings

config

PagerDutyOpen incidents for urgent findings

Microsoft TeamsPost selected findings to a channel

View All (5) Request an integration

Remediation tracking

Turn findings into owned, trackable work for remediation.

JiraCreate issues with evidence and owner context

LinearCreate issues with evidence and owner context

ServiceNowCreate incidents with evidence and owner context

View All (5) Request an integration

Evidence & compliance

Retain evidence for audit, GRC analytics, and reporting.

Amazon S3Archive evidence and findings

Google Cloud StorageArchive evidence and findings

Azure Blob StorageArchive evidence and findings

View All (5) Request an integration

Active cards prove flow

Stats on the connected card show data is actually moving, not just configured.

One affordance per state

Connected gets config; available gets a single dashed add target.

View all expands in place

The long tail unfolds inside the section — no context switch to browse it.