Building
Saved views
The pages the assistant builds — what they're made of, where their numbers come from, and how to change them.
A saved view is a page in your sidebar: a board, a dashboard, a table, a form, a report. It is stored as a layout of components, each bound to a query. Nothing is a screenshot — open a view tomorrow and it shows tomorrow’s data.
Asking for one
Describe the page, not the components.
A page for the sales meeting: total pipeline value at the top, a board grouped by stage, and a list of everything that’s slipped since last week.
You’ll get a view with a stat, a board and a table, placed in a sensible order and added to your sidebar. Then refine it in place: “move the total to the right”, “colour the board by owner”, “drop the slipped list”.
What a view is made of
Components you can ask for by name:
| Group | Components |
|---|---|
| Numbers | stat, progress, chart, line_chart |
| Records | table, list, record, descriptions, tag_group |
| Boards & time | kanban, calendar, timeline, steps |
| Structure | section, grid, tabs, collapse, divider |
| Relationships | tree, network, orgchart |
| Content | markdown, text, image, alert, result, empty |
| Live | ai_chat — an embedded assistant scoped to this page |
You never have to memorise this list. Ask for “a board”, “a chart of that over time”, “a little chat box on the page” and the right component is chosen.
Where the numbers come from
Every component that shows data is bound to a data source. A data source is one of:
- a query over your types — “all leads where stage is not won or lost”,
- a direct query — for shapes that need joining or grouping in ways a simple filter can’t express,
- a tool call — data fetched live from a connected integration, so a view can show something that doesn’t live in CogniWork at all.
Data sources are named and reusable, so two components on the same page can share one query instead of running it twice.
Live by default
Data sources are re-run every time the page loads. That’s the default and almost always what you want.
A snapshot freezes the data at the moment you save it. Use it for something that must not move — a figure quoted in a board pack, a month-end position. Ask explicitly: “snapshot this view as it stands.”
Editing by hand
Open a view and switch on edit mode. You can:
- reorder and resize components,
- edit text and table cells inline,
- change a component’s title, columns or grouping,
- add or remove components,
- see and edit the query behind any component.
Changes save to the same view the assistant built. There’s no separate “designed” copy to keep in sync.
History
Views keep a history. You can compare a view against an earlier state, see exactly what changed, and revert if a change made things worse. This matters most when you and the assistant are iterating fast on the same page — you can always get back to the version that worked.
Placing and sharing
- Sidebar — views appear in your menu; drag them into order, group them under headings, or hide the ones you only reach from elsewhere.
- Share — generate a link to a view for someone who needs to see it. You choose what the link exposes; it doesn’t hand over the workspace.
- Images — ask for a rendered image of a view when you need to paste it into a deck or send it in a message.
When a view shows nothing
Almost always one of three things:
- The filter is stricter than you meant. Ask “what is this table actually querying?” and read it back.
- The data isn’t there yet. Check the type under Data structures.
- The component and the query disagree — the query returns fields the table isn’t asking for. Ask the assistant to reconcile them; it can see both sides.
Next
- AI workers — colleagues that keep views up to date without you.
- Integrations — putting outside data on a page.