New
Labels for sensitive boards, private mode, and dashboards
Boards and docs can now carry a sensitivity label such as Confidential, and a label can switch their exports off. Boards also gain a private mode that keeps everyone's notes face down until the reveal, plus selections you can protect. Projects get dashboards and can group work by type, Reports shows how long work takes, and a doc can now hold a live whiteboard.
- Label a board or a doc Confidential, Internal, or a label your admin defines. A label can switch exports off, and its chip shows at a glance what it allows.
- Private mode on boards: notes stay face down until the facilitator reveals them, in every tab the same person has open, and no one's words are lost when a tab comes back late.
- Dashboards: put Reports' numbers and charts on a dashboard of your own, a project's or the workspace's.
- Work by type: a project's list and board group and filter by task type, and each row and card shows its type.
- Reports opens on any view, slices by your custom fields and shows how long work takes.
- Protect part of a board: a protected selection is locked for everyone else, with a badge on the canvas, until you lift it.
- A whiteboard in a doc: it shows live and read-only, and Look around lets you move about it without leaving the page.
- A huddle posts its card in the conversation, showing who is in the call, and the card keeps its facts after the call ends.
- Retention rules and legal holds now cover boards too, and a legal hold's export comes in parts you can download one by one.
- A board shared by link can be embedded read-only on any website.
- Tables over the API: a table's fields, views and row comments, plus creating, changing, deleting and restoring a table, through the REST API and as tools for your AI agents.
- Board exports say what they left out. Narrow call tiles keep the first word of each name and mark a guest, an agent or an invitee.
Before you update: Five database migrations (569 to 573) add retention rules and legal holds, sensitivity labels, dashboards and two calendar columns; make update applies them after taking a backup. Re-run the install command you installed with, then make update. This update also recreates the Postgres container once, now with 256 MB of shared memory, so big tables load under heavy use; the database restarts with a short pause. Update the web app with the server, as make update does, and if you host the web app yourself, deploy this release's web app at the same time; anyone with a tab open should reload. Going back to the earlier release isn't supported: restore the backup make update took. For scripts and integrations: an API token now works with a table itself, acting as the token's member: make, rename, delete and restore a table (/v1/tables, /v1/tables/{id}, /v1/tables/{id}/restore, /v1/tables/trash), its fields and views (/v1/tables/{id}/fields and /v1/tables/{id}/views, each with a batch), and a row's comments and threads (/v1/tables/{id}/rows/{row}/comments); your AI agents get the same operations as tools. New routes cover sensitivity labels (/labels, and /admin/labels for admins), retention rules and legal holds (/admin/retention/rules and /admin/retention/holds), dashboards (/project/dashboards and /project/{project_uuid}/dashboards) and protecting part of a board (/board/protect). Existing routes keep their paths.
Fixes
- A table's webhooks could reach owners who couldn't open the table; fixed.
- A column change is one undo step, and it reaches only people who can open the table.
- Keys typed before a table's cells finish loading are kept, in order.
- Big tables load their rows and sums again when many people read at once on an install, because Postgres now gets more shared memory.
- A held note's words show when its author's tab opens after the round.
- Board dialogs sit above the app, and a ? typed into text on a board stays in the text.
- A failed save is reported once, not several times.
- Using a calendar's secret link is recorded in the admin log.