> 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-folder-scope/configuration-values-reference.md).

# Configuration values reference

Use the table below to record the IDs, names, and emails generated during your manual onboarding setup. These values are used in the commands and configuration steps throughout this guide. For service account emails, refer to the identifiers JSON file you downloaded from the GCP onboarding wizard in Cortex in Phase 1.

| Variable placeholder                         | Value | Description                                                                        |
| -------------------------------------------- | ----- | ---------------------------------------------------------------------------------- |
| `<HOST_PROJECT_ID>`                          |       | The unique ID of the GCP host project where service accounts are created.          |
| `<FOLDER_ID>`                                |       | The numeric ID of the folder to onboard.                                           |
| `<ORG_ID>`                                   |       | The numeric ID of the organization the folder belongs to.                          |
| `<PLATFORM_SA_NAME>`                         |       | The name you assigned to the Platform Service Account in GCP.                      |
| `<SCANNER_SA_NAME>`                          |       | The name assigned to your general Scanner Service Account.                         |
| `<AUDIT_SA_NAME>`                            |       | The name assigned to the Audit Logs Service Account used for log ingestion.        |
| `<CLOUD_VIEWER_ROLE_ID>`                     |       | The unique ID of the custom Cloud Viewer role created at the Organization level.   |
| `<ADS_CONNECTOR_ROLE_ID>`                    |       | The ID for the custom ADS Connector role.                                          |
| `<ADS_OUTPOST_ROLE_ID>`                      |       | The ID for the custom ADS Outpost role.                                            |
| `<AUTOMATION_ROLE_ID>`                       |       | The ID for the custom Automation role.                                             |
| `<DSPM_CONNECTOR_ROLE_ID>`                   |       | The ID for the custom DSPM Connector role.                                         |
| `<DSPM_OUTPOST_ROLE_ID>`                     |       | The ID for the custom DSPM Outpost role.                                           |
| `<DSPM_SCANNER_CONNECTOR_ROLE_ID>`           |       | The ID for the custom DSPM Scanner Connector role.                                 |
| `<REGISTRY_SCANNER_ROLE_ID>`                 |       | The ID for the custom Registry Scanner role.                                       |
| `<SERVERLESS_SCANNER_ROLE_ID>`               |       | The ID for the custom Serverless Scanner role.                                     |
| `<TOPIC_NAME>`                               |       | The name of the Pub/Sub topic created for audit log streaming.                     |
| `<SUBSCRIPTION_NAME>`                        |       | The name of the Pub/Sub subscription created for the audit topic.                  |
| `<SINK_NAME>`                                |       | The name of the Logging Sink created in the Logs Router.                           |
| `<SINK_WRITER_IDENTITY>`                     |       | The unique service account email generated by GCP after creating the Logging Sink. |
| `<OUTPOST_SERVICE_ACCOUNT_EMAIL>`            |       | The `outpost_service_account_mail` value from your Identifiers JSON file.          |
| `<SAAS_COLLECTOR_SERVICE_ACCOUNT_EMAIL>`     |       | The `saas_collector_service_account_mail` value from your Identifiers JSON file.   |
| `<DSPM_SCANNER_SERVICE_ACCOUNT_EMAIL>`       |       | The specific scanner email used for DSPM tasks.                                    |
| `<REGISTRY_SCANNER_SERVICE_ACCOUNT_EMAIL>`   |       | The `registry_scanner_service_account_email` value from your JSON file.            |
| `<SERVERLESS_SCANNER_SERVICE_ACCOUNT_EMAIL>` |       | The `serverless_scanner_service_account_email` value from your JSON file.          |
| `<YOUR_ADDITIONAL_LABELS>`                   |       | Custom key-value tags used to organize resources within Cortex.                    |


---

# 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://cortex-docs.paloaltonetworks.com/google-cloud-platform-manual-onboarding/gcp-manual-onboarding/gcp-manual-onboarding-guide-folder-scope/configuration-values-reference.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.