Data Snowflake ACCESS_HISTORY and Object Lineage

Status: public · Confidence: medium (0.685) · Basis: verified_sources

## TL;DR

Snowflake ACCESS_HISTORY gives data agents source-object, column, and audit evidence for access review and lineage investigation.

## Core Explanation

Data agents often need to answer who touched a dataset, which columns were read, and which downstream objects were affected. ACCESS_HISTORY is a useful Snowflake evidence source because it connects query activity with object and column access rather than relying only on dashboard ownership or warehouse billing signals.

Agents should treat access history as sensitive audit data. A source-mapped answer should include the time window, object identifiers, user or role context, accessed columns, target objects, and any retention or privilege limits that may hide older or unavailable events.

## Source-Mapped Facts

- Snowflake documentation says the ACCESS_HISTORY Account Usage view can be used to query access history for Snowflake objects. ([source](https://docs.snowflake.com/en/sql-reference/account-usage/access_history))
- Snowflake documentation says ACCESS_HISTORY records SQL statements that read data from source objects and columns. ([source](https://docs.snowflake.com/en/sql-reference/account-usage/access_history))
- Snowflake access history documentation says users can audit who accessed sensitive data and when access occurred. ([source](https://docs.snowflake.com/en/user-guide/access-history))

## Further Reading

- [Snowflake ACCESS_HISTORY View](https://docs.snowflake.com/en/sql-reference/account-usage/access_history)
- [Snowflake Access History](https://docs.snowflake.com/en/user-guide/access-history)