> For the complete documentation index, see [llms.txt](https://docs.reo.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reo.dev/integrations/output-integrations/data-export/gcp.md).

# GCP

To securely transfer files into your environment, we use Google Cloud Storage - this keeps your data within your own infrastructure and under your control at all times. To upload files into your environment, we use a service account that we provision on our side. You'll just need to grant it access to your bucket.

**Here’s how it works:**

1. Reach out to your account manager at Reo.Dev to get the service account email we've created for your account.
2. In your GCP project, grant access to that service account:
   * Open the bucket you'd like to upload the data to
   * Under the *Permissions* tab, add the service account email and assign the `roles/storage.objectAdmin` role
   * Share the bucket name back with us

Feel free to reach out to your account manager or drop us an email at <support@reo.dev> in case you hit any blockers.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reo.dev/integrations/output-integrations/data-export/gcp.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.