Tables Overview

Tables define your data models. Each table is a distinct entity (users, products, orders) whose fields declare the columns that records can store. Tables are the foundation of a Sovrium app: pages render their records, forms write to them, automations react to their changes, and the REST/MCP APIs expose them.

A table has at minimum an id, a name, and a fields array. Everything else — primary keys, indexes, constraints, views, permissions, webhooks, and AI exposure — is optional and layered on top.

tables:
  - id: 1
    name: Contacts
    fields:
      - { id: 1, name: email, type: email, required: true, unique: true }
      - { id: 2, name: full_name, type: single-line-text, required: true }
      - { id: 3, name: created_at, type: created-at, indexed: true }

Table Properties

Each entry in the tables array accepts the following properties.

Base Field Properties

Every field — regardless of type — extends a common base. These properties are available on all 49 field types.

Example: a richer table

tables:
  - id: 2
    name: Products
    fields:
      - { id: 1, name: sku, type: single-line-text, required: true, unique: true }
      - { id: 2, name: title, type: single-line-text, required: true, indexed: true }
      - { id: 3, name: description, type: long-text }
      - { id: 4, name: price, type: currency, required: true, currency: USD }
      - { id: 5, name: in_stock, type: checkbox, default: true }
    primaryKey: { type: auto-increment, field: id }
    indexes:
      - { name: idx_products_sku, fields: [sku], unique: true }
    permissions:
      read: all
      create: [admin, editor]
      update: [admin, editor]
      delete: [admin]

Related Pages

• Field Types Overview — all 49 field types by category.
• Permissions — RBAC and per-field access control.
• Indexes & Constraints — primary keys, indexes, CHECK constraints.
• Relationships — linking tables together.
• Views — saved filters, sorts, and grouping.
• Validation — field- and table-level validation rules.
• Webhooks — outgoing HTTP on record events.