Skip to main content

​
Data structure

Your app’s tables and columns are defined through migrations in Build mode. GenieForge keeps data models in sync so the app can create, read, update, and delete records in a structured way. You describe the records you need (requests, clients, sessions), ownership rules, and what each role may see; GenieForge owns the schema work.

​
Where it lives

  • App Blueprint → Migrations and Schema for structure (shared recipe).
  • Project Tables for live rows in the selected project.
Blueprint migrations define structure for every project; rows stay in each project.

​
How to verify

  1. Open App Blueprint → Migrations and Schema for structure.
  2. Open project Tables for live rows in the selected project.
  3. Preview as each role that should read or write those rows.
  4. Confirm deletes through a model tool ask for confirmation before rows are removed.

​
Limits and notes

  • Destructive structure changes can affect live project data; use Versions and rollback carefully and Preview before you publish.
  • You can turn on semantic search on text fields when that fits the app.
  • Real customer data stays in each project; export/import moves recipe, not live rows.
  • Shared tables can follow a person across projects after a grant. They are not the default. Project tables do not need a workspace key.