Screens over your rows, without a front-end project
Drop blocks on a page and bind each one to a table. No query to write, no component to build, and nothing to redeploy when somebody adds a column.
CRM
- A board over any dropdown column
- The lanes are that column's own options, so changing the options changes the board. Drag a card to move the row. Gate a lane on a checkbox and a card that has not met it simply is not draggable, with the reason on it.
- Record pages that hold the whole story
- Fields you can edit in place, related lists that inherit the record they are under, a timeline you can write into, a stepper for the state, and a panel showing which approvals are running and who owes the next move.
- Tiles and charts on the same rows
- A metric is one number, a chart is the same query with a bucket — grouped by a column or by a date grain. They read the rows the work happens in, so the number is current by construction.
- A request portal on a link
- Put a catalog block on a page and publish it: a branded front door listing what people can ask for, with nobody needing an account. Add the collections you are happy for the world to read.
What it does not do
- A public page is read-only and has no viewer, so record pages, related lists, timelines, steppers and the process panel are refused on one — by name, with the reason.
- A table carrying a row policy cannot be served on a public link at all: there is nobody to evaluate the policy against.