> 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/getting-data-into-editable/connect-to-data/configuration-steps/configure-columns.md). # Configure Columns The next step is to configure the columns by setting their general properties, constraints, and other settings. 1. To configure the columns, click on the link as shown below:

2. Configure the first column - EmployeeID as shown in the image below. We have set the input type for EmployeeID column as text, enabled editing, and set it as a mandatory input (since we want it to be the primary key). Other details can be optionally configured if required.

3. Configure the remaining columns (FirstName, LastName, etc.) one by one, wherever applicable. The columns that are not configured are indicated using a red warning symbol, as seen in the above image. You can choose to modify the existing settings or retain the same. 4. Click **Save** to save the configured settings for all columns. Note: For simplicity, we have configured only the ***General*** settings in the image above. In the [following sections](/working-with-editable/manage-columns.md), we will look at some more advanced settings such as lookup & relation, constraints and display. Editable supports the following column input types: * Number * Decimal * Text * Single-select dropdown * Checkbox * Date-Time * Date * Image * Person * URL {% hint style="info" %} By default, the 'Checkbox' column type accepts Boolean values (true/false). To change it, go to the **Constraints** section - Default Value field in the '[Manage Columns](/working-with-editable/manage-columns.md)' window. In the same way, you can set constraints for each column input type under **Constraints** section. {% endhint %} The next step is configuring SCDs which is optional. --- # 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/getting-data-into-editable/connect-to-data/configuration-steps/configure-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.