Artifacts in Snowflake Intelligence¶
Snowflake Intelligence delivers rich, interactive charts and tables as part of its responses. When you find an insight worth keeping, you can save or share it as an artifact. An artifact is a persistent representation of that insight that you can revisit, refresh, and collaborate on without regenerating it. After being created, an artifact preserves the query, visualization, and context so you can return later to see fresh data, or share it with a teammate who sees the same artifact filtered through their own data permissions.
Interactive tables and charts¶
When you ask Snowflake Intelligence a question, the agent generates a response that may include a chart, a table, or both. Charts and tables are interactive, so you can sort, filter, search, and resize directly without asking a new question. In explorer mode, charts and tables are synced so that interactions in one update the other.
Note
Queries default to rolling time windows (for example, “last 30 days” always means the most recent 30 days). If you need a fixed time period, ask with explicit dates such as “show me data from November 15 through November 22.”
Save artifacts¶
When a chart or table contains an insight you want to keep, select Save to create an artifact. The artifact preserves the underlying query, visualization settings, and a data snapshot so it loads instantly when viewed later.
Manage artifacts¶
The artifacts hub is the central place to manage your artifacts. It contains the following tabs:
Saved: All artifacts you’ve saved.
Shared with me: Artifacts shared with you through a link.
The hub displays cached snapshots as tile previews for fast loading. You can select a tile to expand the artifact, see additional context, and start a follow-up conversation. You can also search for saved artifacts by name within the artifacts hub.
Artifacts auto-refresh when you view them more than 12 hours after your last view. You can also refresh manually at any time. The refresh re-runs the original SQL query with your current credentials and updates both the data and the snapshot.
You can ask follow-up questions on any saved artifact. Each follow-up starts a new conversation thread that includes the artifact’s visualization spec, data snapshot, and a summary of the original conversation context. The original conversation stays private and unchanged.
Security and access control¶
Artifacts follow a caller’s-rights model. Every data interaction validates the current user’s permissions at runtime.
The following security behaviors apply:
Saved artifacts are user-scoped: Saved artifacts are private to each user. Other users can only see artifacts that are explicitly shared.
RBAC is enforced: Every refresh and share runs the query under the viewer’s current role and credentials. Two users with different roles may see different results from the same artifact.
Ownership is persistent: Artifacts are tied to the user, not to a specific role or agent. If you lose access to the originating agent, you keep the artifact and can still refresh it as long as you have access to the underlying data.
Artifact lifecycle¶
Saved artifacts persist until you explicitly delete them. Snowflake Intelligence never automatically deletes a saved artifact.
The following table describes what happens when access conditions change:
Condition |
What happens |
|---|---|
You lose agent access |
You can still view and refresh the artifact. Follow-up questions with the original agent are not available. |
You lose data access |
The last cached snapshot remains visible but refresh is unavailable. |
Agent is deleted or modified |
The artifact and its saved query are unaffected. Follow-up questions use the current agent definition, if available. |
When an agent is no longer available, Snowflake Intelligence displays a warning.
Known limitations¶
Single artifacts only: Currently, you can save and share an individual tile per artifact. Collections of multiple tiles aren’t supported.
No user-level sharing permissions: Currently, sharing is link-based and public within the account. You can’t restrict a shared link to specific users.
No folders or labels: Currently, artifacts can’t be organized into groups, folders, or labeled for categorization.