Skip to content

Data Governance for AI and Agents

Guidelines for Snowflake access: users, roles, warehouses, PII and cost controls.

Users and roles

  • Anything automated uses a Service User, never a personal account
  • Every Service User gets a dedicated role that inherits from existing roles for data access (e.g. READ_ONLY)
  • Only the dedicated role can use the Service User's warehouse
  • Create one with the Service User script

Warehouses

Each Service User has a shared or dedicated warehouse, reachable only through its role. This makes cost attributable per service and keeps it off warehouses meant for other uses (Looker, Count).

PII

  • Granted only when the use case demands it. See Request access to PII
  • Service Users need IP whitelisting regardless of PII access
  • Agent connections must be identifiable
  • Access is audited every 3-6 months and revoked when unused

Cost controls

  • Query timeout and queue timeout: 10 minutes on all non-data-team warehouses
  • Usage is monitored in the Looker cost monitoring dashboard

Agents and data leakage

Agents can leak PII or sensitive data without malicious intent. Connect them through a Service User with a dedicated role and scope access to the minimum the use case needs.