> For the complete documentation index, see [llms.txt](https://docs.tonic.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tonic.ai/app/generation/database-view/database-view-column-comment.md).
# Commenting on columns
{% hint style="info" %}
**Required license:** Professional or Enterprise
{% endhint %}
From **Database View**, you can add comments to columns. For example, you might use a comment to explain why you selected a particular generator or marked a column as sensitive or not sensitive.
## Creating a new comment
If a column does not have any comments, then to add a comment:
1. In the **Applied Generator** column, click the comment icon.
2. In the comment field, type the comment text.
3. Click **Comment**.
## Responding to existing comments
When a column has existing comments, the comment icon is green. To add comments:
1. Click the comment icon.\
\
The comments panel shows the previous comments. Each comment includes the comment user.
2. In the comment field, type the comment text.
3. Click **Reply**.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.tonic.ai/app/generation/database-view/database-view-column-comment.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 `build a script that syncs our docs to a CMS` 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.