> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/warehouse/google-bigquery/enable-multi-project-support.md).

# Enable multi project support

It is possible to query datasets stored in other Google Cloud Project than in the "primary" project that is configured. BigQuery compute cost will still be charged in the "primary" project, but it gives you more flexibility to organize your Warehouse to use multiple projects.

To activate multi project support, you need to do the following in Google Cloud console:

a. Activate the [Cloud Resource Manager API](https://console.developers.google.com/apis/api/cloudresourcemanager.googleapis.com/overview) **on the primary project ID** configured in Whaly

b. Give IAM permissions (Role: **`BigQuery User`** or **`BigQuery Admin`**) to the Whaly Service Account in each of the projects you want to add

c. (only if granted role is **`BigQuery User`** in previous step) For each datasets to the Datasets stored in secondary projects [grant access to Whaly](/warehouse/google-bigquery/grant-access-to-bigquery-datasets.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.whaly.io/warehouse/google-bigquery/enable-multi-project-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.