> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex/vincent/projects/work-with-conversations-and-outputs-in-a-project.md).

# Work With Conversations and Outputs in a Project

Learn how conversations work in a Project in Vincent, why you can read but not continue a colleague's, and how to save your work as a shared output.

#### Summary

Learn how conversations work inside a Project in Vincent, why you can read a colleague's conversation but not continue it, and how to save work as an output your team can find.

### Why This is Important

A Project's value is that the team's thinking is visible. A conversation a colleague ran last month is there to read, and the draft they produced is there to use, so the same question is not asked twice and the same document is not drafted twice.

Two rules shape how that works in practice: conversations belong to the person who started them, and work becomes a shared output only when someone says it is ready.

### How Conversations Work in a Project

A conversation inside a Project behaves like any other Vincent conversation. Skills, document upload, web sources, Agentic Mode, and workflows all work the same way; they are simply contained in the Project. A conversation started by a workflow carries a badge showing which workflow produced it.

Open the Conversations tab to see every conversation in the Project, including those started by other members.

{% hint style="warning" %}
You can read a colleague's conversation, but you cannot continue it. Each conversation is owned by the person who started it. Vincent has no live presence layer, so two people working in the same conversation at once would have no way of knowing about each other. To build on a colleague's work, start your own conversation. 
{% endhint %}

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FA5EbFcmfhQiB6Jmov06r%2FScreenshot%202026-09-30%20at%2012.43.12%E2%80%AFPM.png?alt=media&amp;token=7be07990-f9d3-45de-8821-0b5b96e81337" alt=""><figcaption><p>Project conversations stay inside the Project. They do not appear in your main left-hand conversation panel.</p></figcaption></figure>

### What Outputs Are, and How They Differ From Files

Files are what you bring into a Project. Outputs are what you create in it.

Work you produce in Vincent, a draft, a memo, a table, sits inside the conversation where it was made, which is a poor place for a colleague to find it. Saving it as an output lifts it out of that conversation and into the Project's Outputs, where every member can see it.

### How to Save Work as an Output

1. In the conversation, open the draft or result you want to keep.
2. Where you would normally download it, choose&#x20;
3. It appears in the Project's outputs list.

This is deliberately a manual step. If every interim draft saved automatically, the outputs list would fill with five versions of the same document and stop being useful. You decide when something is finished enough to share.

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FHCPPB0iAZpzsbcFmjeg2%2FScreenshot%202026-09-30%20at%2012.46.47%E2%80%AFPM.png?alt=media&amp;token=05ef7d15-937b-475b-9364-774b071c3982" alt=""><figcaption><p>Save completed drafts or results to your project's outputs list by choosing Save to Outputs from the download menu. Output saving is intentionally manual so you control which final versions are saved and shared with your team.</p></figcaption></figure>

{% hint style="info" %}
**Note:** Members can view and download an output. Outputs cannot be edited in the platform, because an output is meant to be work in its final form. To revise it, produce a new version and save that.
{% endhint %}

### Best Practices & Pro Tips

Save an output at the point you would have emailed it. That is the moment the work stops being yours and starts being the team's, and it is the cleanest test of when the manual save is worth making.

When you build on a colleague's conversation, say so in your own. Because you cannot continue their thread, the connection between the two pieces of work is otherwise invisible. One opening line naming what you are picking up keeps the record readable for whoever comes third.

#### Related Articles

* [Analyzing a Contract](/vincent-by-vlex/vincent/core-workflows/analyze-a-contract.md)
* [Integrating Your Firm's Data with Vincent](/vincent-by-vlex/vincent/core-workflows/integrating-your-firms-data-with-vincent.md)

**What's Your Next Step?**

| **New to Vincent?**                                                                                                                                                                                        | **Already a Vincent Customer?**                                                                                                                            |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [See how Vincent can transform your practice. **Request a personalized demo**.](https://vlex.com/book-a-demo?utm_source=website\&utm_medium=organic\&utm_campaign=web_trial_homepage\&campaign_id=4270741) | [If you still have questions or need help with a specific feature, our team is here to assist. **Contact our Support team**.](https://vlex.com/contact-us) |