> For the complete documentation index, see [llms.txt](https://docs.editable.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.editable.io/working-with-editable/explore-data/pin-columns.md).
# Pin columns
When there are too many columns in the table and you want to freeze a few important ones, you can pin them. When you pin a column, it moves to the first position. Use this option to freeze the key columns to the left so that you can focus on them.
1. Hover over the column header you want to pin, then click the three-dot menu and select **Pin Column** to pin it to the left. We will pin the 'Employee ID' column here.
Pin column
2. To unpin the column, choose **Unpin Column** from the same menu on the header.
Unpin column
3. You can pin multiple columns as shown below.
Pin multiple columns
4. To unpin all of them, select **Unpin All** and the columns will return to their original positions.
Unpin all columns
---
# 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.editable.io/working-with-editable/explore-data/pin-columns.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.
