# Grid Page

A Grid Page is a page where you can easily arrange an execution result of the SQL and Chart created in a Doc Page in a grid layout.

## Key Features

* Intuitive GUI manipulation:
  * Allows users to freely arrange, reorder, resize, and drag & drop various components, including chart components.
* Realtime-collaboration:
  * Reflects changes made by other users on the grid immediately. (Note: Chart settings, etc., are not shared until explicitly saved.)
  * Enables users to add comments.
* Parameter:
  * Enables users to place parameters and operate them easily.
* Explorer:
  * Allows users to use the Explorer to gain further insights into their data.
* Cross Filter (Beta):
  * Enables linking common legends and axes across multiple charts to synchronize data display targets.
  * For configuration constraints and other details, see [Cross Filter](/data-exploration/notebook/grid-page/cross-filter.md).

## Type of Components

The components that can be placed in the grid are as follows:

* Heading
  * A heading component with three levels can be used to separate titles and sections.
* Text
  * Rich text that can be used for documentation.
* SQL result table
  * A table that displays SQL results created in a Doc Page.
* Chart
  * Allows users to place any chart created in a Doc Page.

## About Synchronization of Component Settings

Certain settings are synchronized between the Grid Page and Doc Page, while others remain independent.

* Synchronized with Doc Page:
  * Chart settings (e.g., axes fields, chart type)
* Not Synchronized with Doc Page:
  * Component settings (e.g., header display, component title)


---

# Agent Instructions: 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:

```
GET https://docs.codatum.com/data-exploration/notebook/grid-page.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.