> 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/manage-configuration-changes.md). # Manage configuration changes If you modify the GCP cloud instance configuration in Cortex after the initial setup, such as enabling or disabling security capabilities or audit log collection, your GCP environment will not automatically update. Because this is a manual onboarding deployment, any changes made within Cortex require corresponding manual updates within your GCP account. * **When enabling new capabilities**: You must return to GCP to provision the additional resources, policies, or permissions required to support that specific feature. * **When disabling capabilities**: To maintain a secure and minimalist cloud footprint, you should manually remove or revoke the specific GCP resources and permissions associated with that deactivated feature. Always ensure your GCP permissions and resource deployments mirror your active Cortex configuration to prevent integration gaps or unnecessary permission exposure. --- # 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/manage-configuration-changes.md?ask=&goal= ``` `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.