Artifacts are results you can continue working with: sortable tables, documents, email drafts, and explorable network graphs.
Artifact types
| Type | Common use | Available work |
|---|---|---|
| Table | Lists, comparisons, and rankings | Sort, filter, select, export, and act on rows |
| Document | Briefs, summaries, and reports | Read, copy, save, and link to entities |
| Email draft | Outreach and introductions | Edit recipients and content, save, or send manually |
| Network graph | Exploring how entities are related | Expand relationships and open the full network view |
A table update can revise an existing table instead of producing a separate result.
Saving artifacts
Saving an artifact gives it a name and a visibility setting:
- Private artifacts start with owner-only access.
- Share lets the owner select individual workspace members who may view the artifact.
- Workspace sharing makes the artifact available to all current workspace members.
Research artifacts and email drafts produced by Situation Work also inherit access from their Situation. The viewer must be an active member, hold SITUATION_ACCESS, and be allowed to open that Situation while Intelligence is enabled. Appearing in an email, being linked to a person record, or receiving Attention does not grant access. Revoking the permission removes inherited access; an independent share from the owner still applies.
Selected and inherited viewers can read the artifact. Ownership is still required to edit it, change sharing, delete it, or send its email draft. Removing a selected viewer does not remove access they also have through workspace sharing or a Situation.
The artifact then appears in Artifacts and can be used in later work. Save a copy creates a separate artifact when the original result should remain unchanged.
Deleting artifacts
Delete is in the owner’s actions rail, whether or not the artifact was saved. It removes the artifact for you and for the assistant: a later request that reaches for it finds nothing, and the chat that produced it shows it as not found.
The conversation that made the artifact still describes making it. Asking that chat about the artifact afterwards can produce a confused answer, since the work it is describing is gone. Deleting cannot be undone.
Tables
Table artifacts open in an interactive grid. You can:
- search, filter, and sort rows;
- choose which columns are visible and change their order;
- select rows and add their entities to an Entity list;
- create or copy entities when a result is not already in the destination workspace; and
- export the result as CSV.
Entity references inside cells remain links to the underlying entities. Columns produced through analysis, such as a fit score or rationale, are marked as generated so they remain distinct from workspace data.
Persisted tables are limited to the first 10,000 rows. Havilo marks a result when it has been truncated; export the original result or narrow the question when every row is required.
Documents
Document artifacts present briefs, reports, and other written results in Havilo's document view. Generated documents are currently read-only: you can copy their contents, save the artifact, save a separate copy, change its visibility, and connect it to entities, but you do not edit the generated document in place.
Notes are the editable, collaborative documents in the workspace. Saving a generated document artifact does not automatically create a Note. See Notes.
Email drafts
Email artifacts open in a composer with recipients, subject, and body filled in. Recipients can retain links to their entities, while every part of the draft remains editable by its owner. Shared viewers see a read-only composer. It is the same composer Mail opens for a new message, so a draft Havilo wrote and a draft you started yourself behave identically.
Saving and sending are separate actions. A saved email remains an artifact. It is sent only when a person chooses Send and selects a send-capable Gmail or Outlook account shared with that workspace.
If mailbox creation or updating fails, the draft stays saved in Havilo and remains visible in its Situation with the failure shown. Its mailbox copy is not reported as ready until the provider operation succeeds.
Network graphs
A network graph starts with one or more entities and renders their actual relationship edges. From there, you can expand adjacent connections, filter the view, and open the full network explorer.
The layout is generated by Havilo from entity and relationship data rather than inferred as prose by the assistant. The view is exploratory and transient; it does not create a saved artifact.
Linked entities
Saved artifacts can carry persistent links to the entities they concern. Havilo can find some links from the artifact itself, such as entity-linked email recipients or entity references in a document. You can also add links manually.
Manual links are editable. Extracted and system-maintained links remain read-only, so their origin is not confused with a person's choice. Table cells use live entity references at render time rather than creating a persistent artifact link for every row.
Entity links follow the artifact's visibility. Linking a private artifact to an entity does not make the artifact visible to the workspace.