> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/writebackextreme/v4.0/product-guide/management-console/schemas.md).
# Schemas
A schema is the collection which contains everything about your use-case. The schema will contain information about the selected database, module, user groups and the configuration of the structure of the write-back table. Whenever you create a new schema you have to choose one of our modules first. Depending on the selected module the setup of your schema will be different.
### Create a new schema
Below you will find the steps to create a new schema. In this example we create a schema with the DATA HELPER module. Click on the first image and a slideshow will show up. use your right arrow to see the next image, use your left arrow to see the previous image.
[](https://appsfortableau.infotopics.com/wp-content/uploads/2024/01/WBEcreateschema.png)[](https://appsfortableau.infotopics.com/wp-content/uploads/2024/01/WBEcreateschema-2.png)[](https://appsfortableau.infotopics.com/wp-content/uploads/2024/01/WBEcreateschema-1.png)[](https://appsfortableau.infotopics.com/wp-content/uploads/2024/01/WBEcreateschema-3.png)
Below you see an animated gif that illustrates the entire process of creating a new schema. At the end of the animation it also shows how to edit an existing field, just by opening the schema, select the field you want to change and save your changes. The fields available to add to your form are listed below.
* Single Line Text
* Paragraph Text
* Number
* Boolean (Yes/No)
* Dropdown Select
* Date/Datetime
---
# 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.infotopics.com/writebackextreme/v4.0/product-guide/management-console/schemas.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.
