Skip to content

AI copilot

The copilot turns a sentence into a table definition. You describe what you need, Smith — the AI service — returns a schema, and you decide what to create.

Requirements

The copilot needs the LURANA_CASE_TABLES_AI permission and a Smith service configured for the workspace. Without either, the entry point is not available.

Ask for tables

  1. Open Case Tables → Tables → Open AI copilot.
  2. Describe what you need, for example an HR system with employees and departments.
  3. While it works, the panel shows a skeleton diagram and Smith is thinking….
  4. The answer contains three things:
  5. an inline ER diagram of the proposal;
  6. a written explanation;
  7. the actions Create all, Edit in designer, and Refine.

The copilot reads your context: from the table designer it works on a single table definition; from a domain it works on a domain model with several tables and their relationships. That is why the same sentence can produce one table or a small set.

Review the proposal

Element What it shows
Single table One box with its columns
Domain model One box per table, with lines for the foreign keys between them

Select the diagram to open it full screen. Sending a refinement appends the new proposal below the previous one, so you keep the trail of what changed.

Act on the proposal

Action Result
Create all Creates the domain if the proposal is a domain model, then each table as Draft, and offers a link to them
Edit in designer Loads the proposal into the schema designer so you can change it before creating anything
Refine Sends a follow-up prompt and shows the new proposal

Nothing is published by the copilot. Tables it creates are drafts like any other: review the columns and types, then publish through the normal flow.

Updating existing tables

From the ER diagram you can also ask for changes to tables that already exist — adding a column, or creating a table that the model is missing. In that case the copilot shows a diff and waits for confirmation.

Safety rules it follows:

  • only the schema is sent to Smith, never row data;
  • nothing is applied or published without your confirmation;
  • a table, column, index, foreign key, or primary key is never removed silently;
  • a table with pending draft changes is not overwritten;
  • a table is never created outside the domain you selected without the create-domain flow.

Dropping and renaming tables or columns through a prompt is out of scope.

Permissions

Permission Allows
LURANA_CASE_TABLES_AI Use the copilot

The full list is in Permission reference.

  • Tables — where the created tables appear.
  • Table schema — reviewing what the copilot proposed.
  • ER diagram — the diagram of an existing domain.