Use your Snowflake data in Agnes, live or copied

What you get

• Choose the freshness

  Live tables are queried in Snowflake; scheduled copies refresh on a timetable. Pick per table.

• Find tables quickly

  Since 20 Aug the setup lets the admin browse the account's schemas and tables.

• Access stays deliberate

  The admin grants tables through data packages, so people get the tables they were given.

How it works

1. An admin connects the Snowflake account in Add data source.

2. The admin browses schemas and tables and registers the ones needed.

3. Each table is set as a live table or a scheduled copy.

4. The admin grants the tables through data packages.

Snowflake account

Schemas and tables

Admin connects in Add data source

Agnes

Registered as

Live tables

Queried in Snowflake

Scheduled copies

• An admin connects the account and grants the tables through data packages
• Since 20 Aug: browse schemas and tables in the wizard

1. An admin connects a Snowflake account in Add data source.
2. The admin registers its tables, and since 20 Aug can browse the account's schemas and tables in the wizard.
3. Tables become live tables, queried in Snowflake, or scheduled copies.
4. The tables are granted through data packages.

Good to know

• 

  NewAvailable
  15 Aug 2026NewCompany data and access

  Bring Databricks data into Agnes, copied or queried live

  An admin connects a Databricks SQL warehouse and registers tables or SQL, refreshed on a schedule or, since 17 August, queried live in the warehouse. Unity Catalog metric views arrive as business metrics.

  Read more →
• 8 Oct 2026Read BigQuery data under each person's own Google accountAn admin can set a BigQuery connection or table to passthrough, so reads run as the asking person and BigQuery's own permissions and masking apply. Chats that read such data become private; reads in shared conversations, someone else's shared agent or Slack channel threads are refused.
• 8 Oct 2026Data shared with your group now opens correctlySome data packages shared with a group looked available but never reached its members, whose queries failed with 'not in your stack'. Those shares now work, and new shares are available to members by default.