Table · reads asset

Assets / equipment

Owned/wished items.

Rows and columns, sortable and filterable.

Build an agent that makes this All page types

Contacts

NameRoleStatus

Camille MarchandClient · LyonConfirmed

Yusuf DemirSupplier · ParisAwaiting

Léa FontaineVenue · BordeauxConfirmed

Tomas BrandtLead · BerlinNew

How it works

1
Every field becomes a column; you choose which to show.
2
Sorting and filtering happen on the data, not just the visible page.
3
Values stay editable in place where the field allows it.

Best for

Comparing many records across many fields.

Not the right choice for

A phone. A table is the first thing that stops working narrow.

Who uses this page

Event agency

Qualifies briefs, prices the obvious, and keeps every run-of-show and supplier straight.

IT services provider

Triages what is actually urgent, and gathers the detail before a human looks.

Internal helpdesk

Deflects the password resets and the “where do I find” so your team does the real work.

Questions

What data does the Assets / equipment page use?

It reads asset records the agent has collected. Owned/wished items. Nothing has to be imported first — the page appears once there is something to show.

Do I have to build or configure it?

No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.

When is a table the wrong choice?

A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.

Does it stay up to date?

Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.