> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/table-columns.md).

# Table Columns

<figure><img src="/files/O0qgFf8BhK9yn6peWU6g" alt=""><figcaption></figcaption></figure>

#### Overview

The Table Columns interface in Docbits is used to specify the columns that appear in data tables for each document type. Each column can be configured to hold specific types of data, such as strings or numerical values, and can be essential for sorting, filtering, and reporting functions within Docbits.

#### Key Features and Options

1. **Column Configuration**:
   * **Column Name**: The identifier for the column in the database.
   * **Title**: The human-readable title for the column that will appear in the interface.
   * **Column Type**: Defines the data type of the column (e.g., STRING, AMOUNT), which determines what kind of data can be stored in the column.
   * **Table Name**: Indicates which table the column belongs to, linking it to a specific document type like INVOICE\_TABLE.
2. **Actions**:
   * **Edit**: Modify the settings of an existing column.
   * **Delete**: Remove the column from the table, which is useful if the data is no longer required or if the document type's data structure changes.
3. **Adding New Columns and Tables**:
   * **Add New Table Column**: Opens a dialog where you can define a new column, including its name, whether it is required, its data type, and the table it belongs to.
   * **Create New Table**: Allows the creation of a new table, defining a unique name that will be used to store data related to a specific set of document types.

<figure><img src="/files/qmMXE69BRDu8NX6IeXac" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/JawW37Pl9TbkQchFxHdh" alt=""><figcaption></figcaption></figure>

This section is vital for maintaining the structural integrity and usability of data within the Docbits system, ensuring that the data extracted from documents is stored in a well-organized and accessible manner.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/settings/global-settings/document-types/table-columns.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.