Artifacts¶
An artifact is something Adverity Atlas produces that you keep, a dashboard, a slide deck, a report, a data export. You create them from a conversation, refine them by asking, and share them with people who can view or edit.
What you can create¶
Adverity Atlas produces four kinds of artifact, each suited to a different job:
Data apps: Interactive dashboards backed by live queries, filters, charts, and metrics that refresh against your warehouse
Presentations: Slide decks in your brand design, exportable to PowerPoint
Reports: Markdown write-ups, for a formatted document you can read and edit
Data exports: CSV files, for the raw rows behind an answer
Whichever you create, sharing works the same: send it to a teammate as Read only or as a Collaborator.
How artifacts work¶
Create from Chat: Ask for it in a conversation
Refine by asking: “Make it a line chart”, “add a country filter”
Share: Send it to teammates as Read only or Collaborator
Download: Export to PowerPoint or CSV
Every artifact remembers the conversation and the specific message it came from, so you can trace an output back to the question that produced it, and pick the conversation up again to take it further.
Note
Artifacts are independent of automations. You create them from chat, and an automation can also produce them on a schedule, a report every Monday, for instance. Either way they behave the same once created.
Versions¶
Editing an artifact creates a new version rather than overwriting. A new artifact starts at version 1, and each edit adds one, so a data app refined five times is at version 6. That version number is part of how anyone viewing a live copy knows to refresh.
Adverity Atlas retains 50 versions per artifact. Once an artifact passes that, the oldest are pruned, except version 1, which is always kept so the original stays restorable however long the edit history gets.
Going back to an earlier version¶
Ask in the conversation to put an artifact back to an earlier version, for example “restore the deck to version 3”. Adverity Atlas restores it and tells you which version it came from.
Restoring is non-destructive. It appends a new version carrying the older content instead of overwriting anything, so the restore is itself undoable: restore the version you were on before and you are back. Content and configuration move together, so a data app comes back with the queries that match its layout, never one without the other.
Note
Restoring changes content only. Publishing state and share links are left as they are, so a restore never republishes a private artifact and never revokes a link someone is using.
Restoring an artifact requires the same edit rights as editing it. Someone who was given a read-only share cannot restore it.
Renaming an artifact¶
Ask in the conversation to rename one, for example “rename the deck to Q3 Channel Review”. The new title is what shows in the workspace artifacts list and on the artifact’s own page.
A rename changes the catalog entry only. No new version is recorded and the content is left alone, so a rename never disturbs a published copy or a share link someone is using. It takes the same edit rights as editing the artifact, so a read-only share cannot rename it.
Storage¶
Artifacts are written to the workspace’s configured storage backend, not to your warehouse. If a workspace has no storage set up, configure one first, see Workspaces and storage.
Permissions¶
Roles are cumulative, so the role named is the lowest one that can take the action.
Action |
Required role |
|---|---|
View artifacts in the workspace |
Viewer |
Create and edit artifacts |
Editor |
Share and publish |
Editor |
Delete artifacts |
Editor |
Artifacts are the one thing an Editor can delete without an Admin: they are working output, so whoever can create one can clear it away again. The reach is your own artifacts, published ones, and any shared with you. Being a participant in the conversation that produced an artifact lets you read it, never delete it, and the same holds for an artifact opened to everyone in the workspace.