Stay organized with collections
Save and categorize content based on your preferences.
ORGANIZATION_OPTIONS_CHANGES view
You can query the INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES view to retrieve
real-time metadata about BigQuery configuration changes in an
organization.
This view reflects organization-level and project-level configuration changes
made after January 31, 2024.
Required permissions
To get the permission that
you need to get the configuration changes,
ask your administrator to grant you the
BigQuery Admin (roles/bigquery.admin)
IAM role on your organization.
For more information about granting roles, see Manage access to projects, folders, and organizations.
This predefined role contains the
bigquery.config.update
permission,
which is required to
get the configuration changes.
When you query the INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES view, the query
results contain one row for each configuration change in an organization.
The INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES view has the following schema:
Column name
Data type
Value
update_time
TIMESTAMP
The time the configuration change occurred.
username
STRING
For first-party users, it's their user email. For third-party users, it's
the name that users set in the third-party identity provider.
updated_options
JSON
A JSON object of the configuration options users updated in the
change, containing the previous and the new values of updated fields.
project_id
STRING
The project ID. This field is empty for organization-level
configuration changes.
project_number
INTEGER
The project number. This field is empty for the organization-level
configuration changes.
Data retention
This view contains sessions that are running, and the history of sessions
completed in the past 180 days.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[[["\u003cp\u003eThe \u003ccode\u003eINFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES\u003c/code\u003e view provides real-time metadata on BigQuery configuration changes at both organization and project levels.\u003c/p\u003e\n"],["\u003cp\u003eThis view is subject to the Pre-GA Offerings Terms, meaning it is available "as is" with potentially limited support, and covers changes made after January 31, 2024.\u003c/p\u003e\n"],["\u003cp\u003eAccessing configuration change data requires the \u003ccode\u003ebigquery.config.update\u003c/code\u003e permission, typically granted through the BigQuery Admin IAM role.\u003c/p\u003e\n"],["\u003cp\u003eEach row in the view represents a single configuration change, detailing the update time, user, modified options (with old and new values), project ID, and project number.\u003c/p\u003e\n"],["\u003cp\u003eThe data displayed is scoped to the region where the query is executed, using the format \u003ccode\u003eregion-REGION.INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES\u003c/code\u003e, and it retains data for the last 180 days.\u003c/p\u003e\n"]]],[],null,["# ORGANIZATION_OPTIONS_CHANGES view\n=================================\n\n|\n| **Preview**\n|\n|\n| This feature is subject to the \"Pre-GA Offerings Terms\" in the General Service Terms section\n| of the [Service Specific Terms](/terms/service-terms#1).\n|\n| Pre-GA features are available \"as is\" and might have limited support.\n|\n| For more information, see the\n| [launch stage descriptions](/products#product-launch-stages).\n| **Note:** To get support or provide feedback for organization-level and project-level configuration changes, contact [bq-project-config-service@google.com](mailto:bq-project-config-service@google.com).\n\nYou can query the `INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES` view to retrieve\nreal-time metadata about BigQuery configuration changes in an\norganization.\nThis view reflects organization-level and project-level configuration changes\nmade after January 31, 2024.\n\nRequired permissions\n--------------------\n\n\nTo get the permission that\nyou need to get the configuration changes,\n\nask your administrator to grant you the\n\n\n[BigQuery Admin](/iam/docs/roles-permissions/bigquery#bigquery.admin) (`roles/bigquery.admin`)\nIAM role on your organization.\n\n\nFor more information about granting roles, see [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access).\n\n\nThis predefined role contains the\n` bigquery.config.update`\npermission,\nwhich is required to\nget the configuration changes.\n\n\nYou might also be able to get\nthis permission\nwith [custom roles](/iam/docs/creating-custom-roles) or\nother [predefined roles](/iam/docs/roles-overview#predefined).\n\nSchema\n------\n\nWhen you query the `INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES` view, the query\nresults contain one row for each configuration change in an organization.\n\nThe `INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES` view has the following schema:\n\nData retention\n--------------\n\nThis view contains sessions that are running, and the history of sessions\ncompleted in the past 180 days.\n\nScope and syntax\n----------------\n\nQueries against this view must have a [region qualifier](/bigquery/docs/information-schema-intro#syntax).\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e: any [dataset region name](/bigquery/docs/locations). For example, `US`, or `us-west2`.\n\n\u003cbr /\u003e\n\nExamples\n--------\n\nThe following example retrieves all changes of the\n`default_query_job_timeout_ms option` option: \n\n```googlesql\nSELECT\n *\nFROM\n `region-\u003cvar translate=\"no\"\u003eREGION\u003c/var\u003e`.INFORMATION_SCHEMA.ORGANIZATION_OPTIONS_CHANGES\nWHERE\n updated_options.default_query_job_timeout_ms is not null;\n```\n| **Note:** `INFORMATION_SCHEMA` view names are case-sensitive.\n\nThe result is similar to the following: \n\n```\n+----------------+------------+-------------------------+-----------------+------------------------------------------------------------------------------------------------------------------+\n| project_number | project_id | update_time | username | updated_options |\n|----------------|------------|-------------------------|-----------------|------------------------------------------------------------------------------------------------------------------|\n| 4471534625 | myproject1 | 2023-08-22 06:57:49 UTC | user1@gmail.com | {\"default_query_job_timeout_ms\":{\"new\":0,\"old\":1860369},\"default_time_zone\":{\"new\":\"America/New_York\",\"old\":\"\"}} |\n|----------------|------------|-------------------------|-----------------|------------------------------------------------------------------------------------------------------------------|\n| 5027725474 | myproject2 | 2022-08-01 00:00:00 UTC | user2@gmail.com | {\"default_query_job_timeout_ms\":{\"new\":1860369,\"old\":1860008}} |\n+----------------+------------+-------------------------+-----------------+------------------------------------------------------------------------------------------------------------------+\n```"]]