> For the complete documentation index, see [llms.txt](https://help.pump.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pump.co/gcp-joining-pump/getting-started-with-gcp/step-2-authorize-pump.md).

# Step 2 - Authorize Pump

### Prerequisites[​](https://docs.vantage.sh/connecting_gcp/#prerequisites) <a href="#prerequisites" id="prerequisites"></a>

Before you begin, ensure you have the permission to modify Billing settings within GCP for the projects you want to move to Pump.

### Join Pump <a href="#create-a-billing-export" id="create-a-billing-export"></a>

To onboard on Pump, you must fill out the GCP Account Verification form (shown below) on the onboarding modal so we can provision a GCP sub-billing account under your company's name.[​](https://docs.vantage.sh/enabling_gcp_billing_export/#create-a-billing-export)

<figure><img src="/files/7Rzd1DWq5eerkptL1zFX" alt=""><figcaption></figcaption></figure>

It can take up to 3 hours for the subaccount to be provisioned and appear in your [GCP console](https://console.cloud.google.com/billing/projects). You will  then see a sub-billing account with the Pump prefix ("C012"). Using the Actions column, you can then switch your projects to the new billing account. Within an hour, your projects will appear in your Pump account under "Settings > Integrations".

<figure><img src="/files/CwnYkgygyL3MgUle6I9S" alt=""><figcaption></figcaption></figure>


---

# 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://help.pump.co/gcp-joining-pump/getting-started-with-gcp/step-2-authorize-pump.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.