> ## Documentation Index > Fetch the complete documentation index at: https://docs.cora.ai/llms.txt > Use this file to discover all available pages before exploring further. # Work with Artifacts in Cora > Find, open, and share saved Cora outputs: documents, dashboards, presentations, surveys, checklists, files, and links. Artifacts are the saved outputs Cora keeps for you: briefs, dashboards, presentations, surveys, checklists, files, and links. Agents and chat create most of them. You open them later from the **Artifacts** page. For how artifacts sit next to signals and agents, see [Core Concepts](/getting-started/core-concepts). ## What an artifact is An artifact is a saved output attached to an account or to the workspace. Open **Artifacts** from the nav to see everything in the workspace. Open an account and go to its **Artifacts** tab to see only that account's items. Artifacts are not agent runs, and they are not signals. A run is one execution of a workflow. A signal is an event Cora detected. An artifact is the thing you keep. ## Types Use **Filters** on the **Artifacts** page to show specific types. The filter labels are: * **Document.** Markdown you can read in Cora, such as a meeting prep doc, a QBR summary, or an account brief. Chat and agents both write these. * **Dashboard.** Live charts and tables over your warehouse data. Ask Cora in chat when you want one. You can pin a dashboard to **Analytics**. * **Presentation.** An in-app slide deck, such as a QBR or a book review. Ask Cora in chat when you want one. Chat shows a preview. Reopen it from **Artifacts** with the **Presentation** filter, then **Present** from the player. You cannot pin a presentation to **Analytics**; that stays dashboards. * **Survey** and **Survey Response.** A **Survey** is the reusable template. A **Survey Response** is a completed set of answers, attached to the account you sent the link for. Building, sending, and reporting on surveys is covered in [Surveys](/using-cora/surveys). * **Task List.** A checklist you work through. It is not an agent. An agent is a workflow that can run on its own. A task list is a list of items to complete. * **File Upload** and **External Link.** Files people attach, and links out to Drive or the web. ## How they get created Most artifacts start in one of three ways: * **Ask Cora in chat.** For example, ask for a prep doc, an account brief, a dashboard, or a presentation or QBR deck. Cora saves the result as an artifact. * **An agent writes one.** When a task's output is a document, dashboard, presentation, or similar deliverable, that output is saved as an artifact on the account or workspace. * **You build a survey template.** On the **Artifacts** page, click **New Template**, select **Survey**, and save it. See [Surveys](/using-cora/surveys) for the rest of that flow. Generating an artifact counts as an [Action](/getting-started/actions-and-usage). Opening or downloading one Cora already created does not. New documents and dashboards are private to you by default — see [Sharing](#sharing) below to change that. ## How to find them On the **Artifacts** page you can: * Filter by type with **Filters** (the **Artifact Type** list above) * Search with **Search artifacts...** * Open an item to read it * Download a file when Cora offers **Download** * Pin a dashboard to **Analytics** with **Pin to Analytics** On an account, the **Artifacts** tab shows that account's items with the same types. ## Sharing Documents and dashboards are **private to you by default**: only you can see one until you decide otherwise. There are two independent things you can do to widen access, and you can combine them: * **Change visibility** between **Private** (you, plus anyone you've added below) and **Organization** (your whole team). * **Add specific people**, regardless of which visibility you're on. Adding or removing someone never changes the Private/Organization setting — it just widens or narrows who, specifically, can see a private item. ### From chat If you want something visible to your team right away, say so when you ask for it: *"Save this as a doc on the account, and make it visible to the whole team."* You can also change visibility, or add and remove specific people, later without leaving chat, as long as you're the one who created it: *"Share my Q3 QBR summary with Alex."* *"Make that dashboard visible to the whole team."* *"Take Alex off that doc."* ### From the Artifacts page 1. Open **Artifacts**, find the item, and select the **Share** icon on its row — or open the item's preview and select **Share** there. 2. Under **General access**, choose: * **Private** — only you, plus anyone you've added below. This is the default. * **Everyone in org** — visible to your whole team. 3. Under **People**, add teammates by name or email to give them access directly. This works the same way whether you're set to **Private** or **Everyone in org** — it doesn't switch you out of either one. ## Who can edit Sharing a document lets someone read it. It does not let them change it. * A document, dashboard, or presentation a person created can be edited or deleted by that person or an Admin. Pinning a dashboard to Analytics is an edit. * Something Cora wrote, including an account brief, can be edited by anyone who can already open it. Only an Admin can delete it. * If you can open an item but cannot change it, the page is view only and names who can. Dashboards and presentations are edited in chat. Documents can also be edited on the page. Your change applies right away. You'll only see **Share** on artifacts you created. Cora can only change visibility or people-access on artifacts you own — someone else's private document or dashboard won't show up for you until they add you. ## Slide decks vs artifacts Native presentations live on the **Artifacts** page, same as documents and dashboards. Chat shows a preview. Open the artifact to present. [Google Slides](/using-cora/slide-decks) is still the path when you bring a Drive template or ask for a Google Slides copy. Those copies live in Drive and may not appear on **Artifacts**. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.