> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# See Radar across several Snowflake accounts in one workspace

> Add a cost connection for each Snowflake account, look at Radar for one account or all of them, and keep budgets and alerts per account.

*November 19, 2026*

![The Radar Resources page for Snowflake with the account selector open, listing All accounts (selected), Production US (acme-prod\_us), Production EU (acme-prod\_eu), and Analytics sandbox (acme-sandbox), above the Snowflake warehouses table](https://mintcdn.com/paradime-docs/7a3lHaRfdtArooSd/images/radar-account-selector-all-accounts.jpg?fit=max\&auto=format\&n=7a3lHaRfdtArooSd\&q=85\&s=d3ed29cccee37fe1da977556c3905aea)

A workspace is no longer limited to one Radar cost connection. Add a connection for each Snowflake account that you pay for, then look at Radar for one account or for all of them together.

* **One connection per account.** In **Workspace Settings > Environments > Radar**, click **Add connection** and give the connection a **Connection name**. The first connection is the default. To change the default, open another connection and select **Set as default** in its **More (...)** menu. See [Connect several accounts or projects](https://docs.paradime.io/products/settings/connections/cost-connection/index.md#connect-several-accounts-or-projects).
* **All accounts, or one.** When a workspace has two or more Snowflake cost connections, the Radar cost pages show an account selector. Choose **All accounts** to see every account together, or choose one account for its spend on **Insights**, **Logs**, **Resources**, **Savings**, **Budget**, and **Usage Groups**. The choice stays in the page URL, so a shared link opens on the same account. See [Several Snowflake accounts](https://docs.paradime.io/products/radar/cost-management/index.md#several-snowflake-accounts).
* **Budgets and alerts per account.** Each budget belongs to one account. A built-in Snowflake alert watches the account that you choose, and a custom SQL alert runs on the cost connection that you choose. See [Choose the account an alert watches](https://docs.paradime.io/products/radar/real-time-alerting/configure-alerts.md#choose-the-account-an-alert-watches).
* **A new Ingestion page.** See when Radar last read each cost connection, and click **Retry** when an ingestion failed. See [Ingestion](https://docs.paradime.io/products/radar/cost-management/ingestion.md).
* **One account? Nothing changes.** Your connection is the default, and your budgets and alerts keep working.

You can connect a Snowflake account or a BigQuery project only once in your company, and all the cost connections of a workspace must be on the same warehouse. A BigQuery workspace can have several cost connections, but Radar shows their spend together, with no account selector.

Shipped in Paradime v6.26.3.


## Related topics

- [Snowflake Alerts](https://docs.paradime.io/products/radar/real-time-alerting/snowflake-alerts.md)
- [Radar environment](https://docs.paradime.io/products/settings/connections/cost-connection/index.md)
- [Snowflake cost connection](https://docs.paradime.io/integrations/snowflake/cost-connection.md)
- [Cost Management](https://docs.paradime.io/products/radar/cost-management/index.md)
- [Snowflake Cost Optimization](https://docs.paradime.io/products/radar/cost-management/snowflake-cost-optimization.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.