> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/google-cloud-platform-manual-onboarding/gcp-manual-onboarding/gcp-manual-onboarding-guide-project-scope/phase-5-complete-the-gcp-onboarding-wizard-in-cortex.md).

# Phase 5: Complete the GCP onboarding wizard in Cortex

## Phase 5: Complete the GCP onboarding wizard in Cortex

To complete the onboarding process, return to the GCP onboarding wizard in Cortex. Provide the required GCP scope details and service accounts back to Cortex in the GCP onboarding wizard.

### 5.1 Enter the GCP scope details and service accounts in Cortex

After you have completed phases 2-4 to create the required GCP resources, you return to the GCP onboarding wizard in Cortex. To connect your GCP environment to Cortex, you must provide your GCP scope details and service accounts. You can complete this using one of the two methods below:

* Automated upload: Quickly populate all required fields by dragging and dropping your JSON identifiers file directly into the wizard.
* Manual configuration: Manually input your GCP IDs and your service account emails into the corresponding text fields.

#### 5.1.2 Automated upload

To use the automated upload option, you must first populate the fields in the "manual\_details" section of the identifiers JSON file with the values from your GCP environment.

1. Locate the gcp-identifiers-.json file that you downloaded in step 1.2.
2. Open the file in a local text editor and populate the fields in the "manual\_details" section.
3. Drag and drop the file directly into the GCP onboarding wizard.
4. Verify that the fields in the GCP scope details and Service accounts sections are populated.

#### 5.1.3 Manual configuration

If you have not populated your JSON identifiers file, or prefer to enter details manually, follow these steps:

1. In the GCP onboarding wizard, in GCP scope details, enter the relevant GCP IDs.
2. In Service accounts, enter the required details.

### 5.2 Complete onboarding

In the GCP onboarding wizard, click Save. The new GCP cloud instance is created and is connected to GCP. You can view the GCP cloud instance status in Data Sources & Integrations. The initial discovery scan is started. When the scan is complete, you can view your cloud assets in Asset Inventory.

#### 5.2.1 Troubleshooting

If an error is displayed after clicking Save, you can fix the entries in the GCP onboarding wizard and try saving again.


---

# 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://cortex-docs.paloaltonetworks.com/google-cloud-platform-manual-onboarding/gcp-manual-onboarding/gcp-manual-onboarding-guide-project-scope/phase-5-complete-the-gcp-onboarding-wizard-in-cortex.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.