Assets

Assets is the section where a workspace keeps its own tables: an incident register, a candidate list, a product catalogue, a customer base. The person who needs the table picks its columns — no development, no database change.

Two things set it apart from a spreadsheet in a file: the data lives beside the issues and the threads, and agents work it — reading rows, filling cells, reacting to changes.

Tables, fields, records

• A table belongs to the workspace and is visible to every member.
• A field is a column with a type. The first column is always text and cannot be deleted: it is the record's name, the handle it is known by in lists and links.
• A record is a row. An empty cell is empty — not a zero, not a dash.

A field's type can be changed later. Values are not rewritten in the process: anything that does not fit the new type reads as empty until it is entered again. The exceptions are Link and Image: their type never changes, because the cell holds another record or a file rather than text.

Field types

Views

One table is shown in several ways, and each view is saved as its own tab:

• Grid — the familiar table.
• Kanban — cards in columns by a chosen field.
• Gallery — cards with a picture, when the table has an image field.

A view holds its own setup: filters, grouping, which columns and in what order, which fields show on a card. The first tab in the row is what opens by default, and any view's link can be copied and sent to a colleague.

The record card

A record opens as a card — beside the table, or as a page of its own whose link you can copy and share. The card holds:

• Properties — every field of the record;
• History — who changed what, agents included; kept for 90 days;
• Actions — dispatch an agent on this record, or delete it.

When several people have the table open, or an agent is editing it, the header says so.

Import and export

• CSV import — up to 50,000 rows at a time; columns are mapped to fields by hand, and the extra ones can be left out.
• Paste — paste a selection from another spreadsheet or a table as text, and the parser works out the rest.
• CSV export — exports what the current view shows.

Excel and Google Sheets import, and Excel export, are marked "soon" in the menu.

Agents and tables

To an agent a table is ordinary working material: it reads records, fills cells, and creates rows.

• Ask an agent about selected records — tick the rows and hand them over: review them, check them, fill them in.
• A task on one record — from the record card.
• An Assetflow — dispatches the work itself when something happens in the table.

Assetflows

An Assetflow is a table's automation: the Assetflows tab in the table's header, with the number of those switched on beside it. Its rule reads as one sentence: "When … and … then …".

• When — a record is added, a record is deleted, or a chosen field changes. Several clauses join with "and" and must agree on one kind of event.
• And — optional conditions on the record itself: a field equals, does not equal, is empty, contains, is greater than, is less than.
• Then — one action: dispatch an agent with a prompt you wrote, or start a workflow.

Every Assetflow keeps a Runs journal for 90 days: when it fired, on which record, what triggered it, and how it ended — Pending, Sent, Skipped, or Failed. A skip always states its reason: the rule was disabled or deleted before it ran, its author is no longer a member of the workspace, the dispatch failed, or one change touched too many records at once.

Archiving and deleting

• Archive — the table stays and stays readable, but nothing changes in it any more. Reversible.
• Delete — the table goes, with its fields, records, and Assetflows.

Limits

Next

• How Bounc works — example processes built on tables.
• Workflows — what an Assetflow can start.
• Agents — who works the data on the other side.