BigQuery connector: multi-project support

🎯 What is it?

The BigQuery connector now supports multiple GCP projects within a single connection. Instead of being limited to one project (the service account's default project_id), Dust now automatically discovers and lists all GCP projects accessible by your service account, letting you browse datasets and tables across all of them.

💡 Why is it useful?

Many organizations structure their BigQuery data across multiple GCP projects for governance, billing separation, or organizational reasons. Previously, the connector only accessed a single hardcoded project, forcing you to create multiple connections or miss out on data stored in other projects. This update removes that limitation entirely.

⚙ How does it work?

When you connect BigQuery, Dust now queries all projects your service account can access and presents them in a unified view. You can browse and select datasets and tables from any accessible project without additional configuration.

✨ Concrete Use Cases

Here's how you could use it:

Cross-project analytics: Build agents that combine data from your production project, analytics project, and data warehouse project—all from a single BigQuery connection.

Multi-team access: If your service account has access to projects owned by different teams (marketing, sales, engineering), your agents can now query data from all of them seamlessly.

📈 Benefits for you

• Access all your BigQuery data through one connection instead of managing multiple connectors

• Build more comprehensive agents that work with data across your entire GCP organization

• Simpler setup and maintenance for multi-project BigQuery architectures

🚀 How to access it?

This improvement is available by default for all BigQuery connector users. If you're already using the BigQuery connector, you'll automatically see all accessible projects the next time you browse your data sources. No configuration changes needed.