> For the complete documentation index, see [llms.txt](https://docs.jmapcloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/configuring-project-data/configuring-a-data-table.md). # Configuring a Data Table The configuration panel for each non-spatial data table provides tools to configure the general properties of the table, as it will be presented in JMap NG.
#Description
1Buttons to display the Properties and Filters interfaces.
2Toggle to show or hide the table in the Layers panel of JMap NG applications.
3Click the data source to open its interface.
4

Table name

You can edit it by clicking .

5

Table description

You can edit it by clicking .

6Check this box to enable editing tools. This allows JMap NG users with the relevant permissions to modify the table data.
7

Table fields

You can view field contents by opening the data source interface. Check the fields you want to display in JMap NG applications.

8Click the language button to translate the table name and/or its description.
--- # 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.jmapcloud.io/en/jmap-cloud-portal/user-guide-for-jmap-cloud-portal/configuring-project-data/configuring-a-data-table.md?ask=&goal= ``` `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.