Attached Data Collections
Attach a published Data Collection to this Project so chat and runbooks here can query it.
Audience: builders
Attach here, author elsewhere. This page is the binding side. The collection itself, its sources, scope, and catalog are authored in Data Collections. To use a collection from chat or a runbook once attached, see Using a collection.
Find the Data collections section
Open your Project. Click the Context tab. Pick the Data collections section. The list shows the collections already attached to this Project: name, semantic summary, source count, and build status (Healthy, Populating, or Failed).
The Home Project does not attach Data Collections. Browse and open workspace collections directly from /data-collections instead.
Attach a collection
Click Attach
The button is in the section head, top right. A picker pops open and lists every collection the workspace has published that is not already attached here.
Pick a collection
Search by name or description if the workspace has more than a handful. The picker closes when you click a row, and the row moves into the attached list.
If the picker is empty, either every workspace collection is already attached here, or the workspace has not published one yet. Authors publish from the collection's own page; see Create a Data Collection.
What attachment lights up
Once attached, the collection is reachable from this Project as a first-class reference:
- In chat. The collection appears in the
@picker. Mention it to ground the agent's next answer in its catalog. - In a runbook. Reference the collection by name as part of a
data_domain.intentstep. The agent picks the right tables and columns from the collection's catalog. - Audit. Every query the Project runs against the collection writes a ledger entry, joined to the conversation or work item that triggered it.
The attached row's chip surfaces semantic health at a glance. A Failed chip means the collection's last build did not complete; open the row drawer for the failure detail and a link to the collection's own page.
Refresh and reload
A collection's catalog rebuilds on the collection's own page, not from inside the Project. The attached row reflects the latest published build of the collection, picked up on Project reload. If you need fresh data, work with the collection author to rebuild.
Attached time versus build time. The row shows when you attached the collection here. The semantic build phase shows when the collection itself last rebuilt. The two are independent. Detaching and reattaching does not trigger a rebuild.
Detach
Open the attached collection's row to see the detail drawer. Detach is in the footer; the action shows an inline confirm. Confirming removes the attachment from this Project. The collection itself stays in the workspace and other Projects keep their attachments.
What audit captures
Every attach and detach action writes a ledger entry. Every query the Project runs against the collection writes a ledger entry too, with the collection name, the intent, the tables involved, and the result shape. Open /audit and filter by the Project to walk the trail.
For deeper authoring on the collection side, jump to Create a Data Collection. For asking questions and reading lineage once attached, see Using a collection.