> 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/manage-columns/general.md).
# General
In this category, you can define the following properties:
## **1. Input type**
Specify the input data type to be allowed in each column using this dropdown. EDITable allows the following data types as inputs:
* Number
* Decimal
* Text
* Single-select
* Check-box
* Date Time
* Date
* Image
* Person
* URL
* Email
Input type
Further, you can configure additional properties based on the selected input type.
Example: For number type input, you can set the minimum and maximum allowed values. For single-select type, you can either manually configure the dropdown values or fetch them from a lookup table. These properties are explained in the upcoming sections.
## 2. Allow Edits
Check this box to enable users to edit the column values. Uncheck it to restrict users from modifying the column values.
In the example below, we have made all columns editable.
Primary keys and surrogate keys (in case of configuring Type 2 SCDs) are usually disabled from editing by the users.
Allow Edits
## 3. Required
This box indicates whether the user must enter the values in the column or if they can be left empty. Checking this box will make the column mandatory. You can select which columns you want to be required.
Typically, primary keys and business keys are considered required columns.
Required
We have discussed the general configurations. In the next section, we will explain about setting constraints.
---
# 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/manage-columns/general.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.
