Site · Data
Managing Databases Introduction
Last updated 18 November 2026
Design your own tables: create databases, add and group fields, link and manage them.
A database stores your own data in a table you design: fields of the types you need, grouped and labelled so editors understand them. Use one for anything an Insites module does not already store, such as a list of courses or a product catalog for a non-shop site.
What you can do
| Job | Where |
|---|---|
| Create a database | Creating a database |
| Change its name or settings | Updating a database |
| Add and group fields | Fields and field groups |
| Choose field types | Field types and UI elements |
| Link two databases | Linking databases together |
| Remove every item | Emptying a database |
| Remove the database | Deleting a database |
Fields and their types
Each field has a type, which decides what it stores, and a UI element, which decides how editors fill it in. A Boolean is a toggle, for example, and a GeoJSON is a code box. Give every field a label, a group and a help tooltip, so the form is easy to read.
Example: the databases on a site
Query
{
admin_tables(per_page: 3) {
total_entries
results { name }
}
}Response on the docs site
{
"data": {
"admin_tables": {
"total_entries": 28,
"results": [
{ "name": "ds_page_feedback" },
{ "name": "ds_promo" },
{ "name": "ds_search_event" }
]
}
}
}This ran read-only on the docs.insites.io site on 1 November 2026. Databases are created in the admin; the Data API can read their definitions and manage their items, but cannot change their fields.
Common mistakes
- Building a database for contacts, orders or events. Use the module that already stores them.
- Renaming a field that holds data. Rows keep the old name, so their values are orphaned.
- Leaving fields ungrouped. Ungrouped fields drop to the bottom of the form.