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

# GCP Integrations

Learn how to integrate and manage access to your GCP cloud

If your organization uses Google Cloud Platform (GCP), Apono's GCP integrations can help you securely manage access to your GCP cloud-based services and databases.

<figure><img src="https://1094436629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv6MBfUGvblSdAz31yJXm%2Fuploads%2Fgit-blob-b183b36af6a12fbadc07380eddc82e50a317facd%2FGCP-Integrations-1.png?alt=media" alt="" width="375"><figcaption><p>Google Cloud logo</p></figcaption></figure>

By identifying and transforming existing privileges, Apono can shift your cloud management from broad permissions to on-demand access flows.

Through our GCP integrations, Apono enables you to perform the following access tasks:

* **Limit Access:** Discover existing privileges in GCP and convert them to just-in-time Access Flows.
* **Enable Self-Service Access:** Allow developers to request access to GCP services, buckets, and instances via Slack.
* **Automate Approval Workflows:** Create automatic approval processes for sensitive GCP resources.
* **Restrict Third-Party Access:** Grant third-parties (customers or vendors) time-based access to specific services with MFA verification.
* **Review Access:** Audit user cloud access, permissions granted, and reasons for access across GCP.

\\


---

# 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.apono.io/docs/gcp-environment/gcp-integrations.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.