> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/customize-your-tables.md). # Customize your tables Customize columns and organize records wherever tables appear. Configure the columns, record order, and visual cues in any table display. These settings work in views, pages, and form views. They affect the current table display. They do not change stored records or field values. Use them to show the fields that matter, focus on relevant records, and make important values easier to scan. In **Builder mode**, the column header menu provides additional controls for individual columns.


Customize table columns Show the fields you need. Arrange and hide columns for the current table display.	Customize table columns
Organize table records Sort, filter, group, and aggregate records to focus on relevant data.	Organize table records
Style your tables with conditional formatting Highlight records and values that match your conditions.	Style your tables with conditional formatting

--- # 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.ninox.com/builder-hub/visualize-and-organize-your-data/customize-your-tables.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.