Skip to main content

Artifacts

In Revelry Ai, an artifact is a saved piece of content, whether it came from a conversation, the API, or a Workflow. Artifacts stay in your project, where you can organize, share, and reuse them.

How artifacts are created​

There are four ways to create an artifact:

  1. In chat. Revelry Ai creates artifacts with its artifact tools as part of the conversation (Learn more)
  2. From one chat message, with the message's Save as artifact icon (Learn more)
  3. Through the API, for custom applications (Learn more)
  4. In Workflows, through steps that each run a Skill (Learn more)

Most of the time, it creates artifacts for you during the conversation. You can also save one message exactly as it is.

See Creating artifacts for a comparison of all four.

Categories and artifact types​

An artifact can have an Artifact Type and be filed under a category. Both are optional, and they're set separately.

Artifact type (what it is)​

An artifact type names the kind of content, such as a PRD, roadmap, or user story, and can define its structure and template. Examples: PRD, Roadmap, User Story, Feature Spec.

Category (where it's filed)​

Categories are folders for your artifacts:

  • A project with categories shows them as folders beside its artifact table on wider screens, such as "Product," "Engineering," and "Design"
  • A category's groups narrow who can see the artifacts in it
  • Categories form a tree, with subcategories up to three levels deep
note

Category folders must be turned on for your organization. Contact your Revelry Ai team to enable.

Examples: Product, Engineering, Marketing, Sales.

For example, a "Q1 Roadmap" artifact might have the type "Roadmap" and be filed under the "Product" category. Because type and category are set separately, you can keep one Roadmap in Product and another in Engineering.

Why categorize​

Organization and discovery​

  • With category folders on, pick a category on the project's Artifacts tab to narrow the artifact table to it
  • Related content stays together
  • Artifacts stay organized as you create more

Access control through groups​

An artifact is visible to people with access to its project. A category's groups narrow that further:

  • Give a group access to the "Engineering" category, and its members see the artifacts in it
  • Remove a group's access to the "Sales" category, and those artifacts are hidden from its members
  • You manage access once per category, so there's no need to set it on each artifact

When you save an artifact to Knowledge, you choose separately which groups can see the resulting document. That gives you two layers of access:

  1. Artifact access, from the project and category
  2. Document access, set when you save to Knowledge

Learn more: Saving to Knowledge

Saving from chat​

When you save an artifact from chat, you can choose an Artifact Type to classify it and a category to file it in your project. Neither is required.

You can customize Artifact Types to match your organization's workflow.

What you can do with artifacts​

Once created, artifacts support these actions.

View and edit​

  • Read the full content of any artifact
  • Click Edit to change the text directly
  • Version history: every content change records a version, whether it came from chat, the editor, or the API. The Version History panel in the artifact page's right rail (on desktop) lists versions with author and date. Click one to see a read-only snapshot, and click Restore this version to bring an older one back as a new version, so nothing is lost. Viewing history requires view-content permission, and restoring requires manage-content. Saves that only change the name, type, or category don't create versions.

Update it in chat​

Ask in chat to change an artifact, and the artifact tools update it. Each content change records a new version, so the earlier text stays in the history.

Share​

Share gives you a link to the artifact.

Move to another project​

Move an artifact, along with its connected chat, sub-chats, and documents, to a different project:

  • Change the Project field on the artifact's edit page
  • Artifacts connected to a chat move together with all related content
  • Old artifact links redirect to the new location

Copy, download, and export​

  • Copy copies the artifact's text
  • Download PDF downloads it as a PDF
  • Export to Google Drive sends it to Google Drive once you've connected your Google account. After the first export, the button reads Update in Google Drive
  • In the Export box, choose Github under Select a Source, pick a repository under Select a Project, and click Export to create a GitHub issue from the artifact. Github is offered once your organization adds a GitHub repository as a data source, and you see only the repositories you have access to

A file-based artifact, such as a spreadsheet, opens to a Download File button. You can't edit, share, copy, or save it to Knowledge, and it doesn't keep a version history.

Listen​

Generate an audio narration of an artifact with text-to-speech:

  • Click Generate Audio, then Listen to play it in the built-in audio player
  • Audio is generated with ElevenLabs text-to-speech
note

Contact your Revelry Ai team to enable audio generation. Learn more

Add to a collection​

Collections hold documents, so to put an artifact in one, save it to Knowledge and pick collections under Add to Collection(s).

Artifacts and Knowledge​

Artifacts aren't in Knowledge until you save them there. Chat in the same project can already find and read them.

Opt-in searchability​

When you create an artifact, it's saved to your project, where you can open it. You can also edit, share, and export it, unless it's a file-based artifact, which you can only download. Chat in the same project can find it, but Knowledge Search doesn't return it.

To add an artifact to Knowledge, open it and click Save to Knowledge. When you do:

  1. You choose which groups can see the document
  2. A document is created that mirrors the artifact
  3. Knowledge Search can find the document
  4. Changes to the artifact sync to the document

Learn more: Saving to Knowledge

Choosing what goes into Knowledge​

An artifact you save to Knowledge becomes a document, and documents can go into collections that chat searches. Saving is opt-in, so you choose which content chat can draw on later.

Finding your artifacts​

By project and category​

Click Projects in the left navigation, open a project, and click its Artifacts tab. It lists the project's artifacts in a table with search and filters for type and author. If category folders are turned on for your organization, pick a category in the folders beside the table to narrow the list to that category. Combine a category with a type filter to find, for example, every PRD in Engineering.

In chat, artifact search matches words in artifact names and content within the current project, so you can find an artifact by what it says as well as by its title.

Knowledge Search also finds artifacts that have been saved to Knowledge as documents, by meaning as well as exact words.

note

Only artifacts that have been explicitly saved to Knowledge will appear in Knowledge Search results. Artifact search (by name or content) works on all artifacts, whether or not they've been saved to Knowledge.

From Chat History​

If an artifact was saved from chat, you can find it through that conversation in Chat History.

Next steps​