Quickstart by Hand

Create a table

Open SQL Console in the rail and run:

CREATE TABLE public.work_orders (
  id          uuid PRIMARY KEY DEFAULT gen_random_uuid(),
  title       text NOT NULL,
  site        text NOT NULL,
  priority    text NOT NULL DEFAULT 'NORMAL'
              CHECK (priority IN ('LOW', 'NORMAL', 'HIGH', 'URGENT')),
  status      text NOT NULL DEFAULT 'NEW'
              CHECK (status IN ('NEW', 'ASSIGNED', 'IN_PROGRESS', 'COMPLETED')),
  resolution  text,
  reported_at timestamptz NOT NULL DEFAULT now(),
  CONSTRAINT work_orders_completed_resolution
    CHECK (status <> 'COMPLETED' OR resolution IS NOT NULL)
);

COMMENT ON CONSTRAINT work_orders_completed_resolution ON public.work_orders
  IS 'Write the resolution before completing the order.';

INSERT INTO public.work_orders (title, site, priority, status) VALUES
  ('Compressor trips after 10 minutes', 'Mercado del Norte - Depósito', 'URGENT', 'NEW'),
  ('Yearly maintenance, 4 split units', 'Hotel Salta - Lobby', 'NORMAL', 'ASSIGNED'),
  ('Inverter shows error 31', 'Finca Las Moras - Solar field', 'HIGH', 'IN_PROGRESS'),
  ('Install 2 units in new offices', 'Estudio Paz - 3rd floor', 'LOW', 'NEW');

The rules are in the table itself: the allowed priorities and statuses, and "a completed order has a resolution". PostgreSQL enforces them for every writer: the screens you'll build, the API, a script. The comment on the constraint is the message users will see when they break it.

You can also create tables visually, with Database › New table and Add column.

Expose it

Every table starts hidden. Open Database, choose the public schema's Tables, and in the work_orders row's ⋮ menu choose Endpoints. Turn on GET, POST and PATCH, so screens can read, create and edit orders. Leave DELETE off.

Give the statuses colors

Still in Database, open work_orders and its Columns tab. Open the status column: because it has a CHECK list, its Options list each value. Give each one a label and a color (New gray, Assigned blue, In progress amber, Completed green). Do the same for priority.

Every screen that shows these columns will now use these labels and colors.

Build a kanban board

Open DataViews › New DataView. The wizard asks, step by step:

1. Type: Kanban.
2. General: name it "Work orders".
3. Data: the work_orders table; keep all its columns.
4. Views: Group by status, Card title title.
5. Form, Actions, Security: keep the defaults.

Finish the wizard. The DataView opens as a draft. Click Publish.

Open it in the App

Click App in the rail. Your kanban is in the menu: one column per status, a card per order. Drag a card from New to Assigned: the change is saved at once and recorded in the audit log.

Try a rule

Drag the Inverter shows error 31 card to Completed. PostgreSQL refuses it, because the order has no resolution, and the App shows your constraint's message: "Write the resolution before completing the order."

Open the card, write a resolution, and save. Now it can be completed.

You didn't write any validation in the screen. The rule lives in the database, so it holds everywhere: in this board, in the API, and in anything an AI agent builds later.

Give it to a role

So far only you, the administrator, see the board. Give it to the people who assign the orders:

1. Roles › New role: name it "Dispatcher" and turn on App access.
2. Its Permissions: on the work_orders row, the ⋮ › Allow all actions. A role reads and changes only what it's granted, and seeing a screen grants nothing by itself.
3. Back in DataViews › Work orders › Settings › Security: switch on Dispatcher.

If something is still missing for the role, the DataView's header shows a warning count. Click it: each warning says what is missing and links to the fix, for example a column the role can't read.

To see what a dispatcher sees, go to App and click the eye beside Arrange menu, then Role › Dispatcher › See the App. The App opens as theirs, read-only; Stop takes you back. See App › See as.

Add a dashboard

Open Dashboards › New Dashboard, name it "Operations", and add a Bar chart widget. A widget is a SQL query:

SELECT status, count(*) AS orders
FROM work_orders
GROUP BY status
ORDER BY status

Add a KPI widget with the open orders:

SELECT count(*) FROM work_orders WHERE status <> 'COMPLETED'

Publish, and the dashboard appears in the App next to the kanban.