> For the complete documentation index, see [llms.txt](https://docs.vitaracharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vitaracharts.com/faq/how-to-use-grid-custom-editor.md).
# How to use Grid Custom Editor?
### How we can use Custom Editor in Grid?
**1. Activate Customization:**
* Keyboard Shortcut: Hold down “Ctrl” and left-click on a metric or attribute header.
* Hamburger Menu: Open the menu and select “Format.”
**2. Tabs for Formatting:**
* Column Content Tab: Format content within a column.
* Header Content Tab: Format the column header.
* Images: Insert images via the “Insert” property tab.
* Links: Add URL links using the “Insert” property tab.
* Tables: Build tables with the “Insert” tab and customize each cell.
**4. Format Menu: Apply text formatting, including bold, italics, alignment, and more.**
**5. Toolbox Panel: Quick access for text adjustments and inserting elements like emojis and tables.**
**6. Applying Changes: Click “Submit” to apply changes and click anywhere on the grid to exit the editor.**
**7. Creating Metric/Attribute Groups:**
* Hold “Ctrl” and left-click on headers to group.
* Use the “Column Grouping” button in the editor.
For detailed instructions, visit the full documentation.[https://docs.vitaracharts.com/guideGridFeatures/customeditor.html](/grid-microchart-guide/custom-editor.md)
---
# 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://docs.vitaracharts.com/faq/how-to-use-grid-custom-editor.md?ask=&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.