# Impact Analysis

### Understand what changed — and what it affected

Impact Tracking extends Woven’s observability by connecting to your **Snowflake query history**. It helps you see **who’s using a dataset**, **what queries depend on it**, and **which changes might cause breakages** — all automatically.

> **Turn silent observability into actionable insight.**\
> When schemas change, Woven tells you *what it means* for your data consumers.

***

### Why It Matters

* 🔍 Identify which dashboards or models rely on a table or column
* 👥 See which users or teams most frequently query it
* 🚨 Detect risky changes early — before a downstream failure or incident
* 📈 Build confidence in how data evolves over time

Impact tracking runs continuously in the background — no PR hooks or developer prompts.

***

### Requirements

To enable impact tracking, connect Woven to your **Snowflake account**.

* The integration requires access to the **`QUERY_HISTORY`** and **`ACCESS_HISTORY`** views
* Woven reads only metadata — never query results or raw data
* Permissions can be scoped to a **read-only “WOVEN\_ROLE”**

See [Snowflake Connection](/docs/connections/snowflake.md) → for setup details.

***

### Value Snapshot

Once enabled, you’ll get:

* Slack summaries of **which models or tables are most queried**
* Alerts when a schema change affects **high-impact assets**

***

### Next Steps

👉[ Connect Snowflake](/docs/connections/snowflake.md) →


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.woven.dev/docs/getting-started/observability/impact-analysis.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.