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.
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.
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
In the conversation, open the draft or result you want to keep.
Where you would normally download it, choose
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.
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
What's Your Next Step?
Last updated
Was this helpful?