Add Files to a Project So Your Whole Team Can Use Them
Learn how to add files to a Project in Vincent, what the size and volume limits are, and why a Project's documents do not appear in your Collections list.
Summary
Learn how to add files to a Project in Vincent, what the size and volume limits are, and how a Project's files relate to your Collections.
Why This is Important
Uploading the same document four times because four people need it is the clearest version of the problem a Project solves. Files added to a Project reach every member, across every Vincent workflow, without being re-uploaded per person or per session.
How to Add Files
Open the Project and go to.
Add your files. You can upload them directly, or pull them in from a connected document management system such as iManage or NetDocuments.
Wait for processing to finish before running Vincent against them.

Viewers cannot add or delete files. Editors and the owner can.
File Limits
1 GB per file, the same limit that applies everywhere in Vincent.
10,000 files per Project.
How a Project's Files Relate to Your Collections
This is the most common point of confusion, so it is worth stating plainly.
A Project's files are held in a collection behind the scenes, but that collection is internal. The files appear in the Project and nowhere else; they do not show up in your Collections list.
Two consequences follow:
A Project's document set cannot be copied out to a Collection.
A Collection cannot be turned into a Project.
A Project is not a document management system. You can bring a file in from your DMS, but the connection is not live. If a document becomes a later version in your DMS, that version has to be added to the Project yourself.
Best Practices & Pro Tips
Add the core file set before you invite anyone. A member who opens an empty Project has nothing to orient them, and the first instinct is to upload their own copy of a document that is about to arrive anyway. Load the spine of the file first, then share.
Decide where the authoritative version lives, and say so in the description. Because versions are not synced from a DMS, a team needs one sentence of convention about whether the Project or the DMS is the source of truth for the current draft. Put it in the Project description where everyone sees it.
Related Articles
What's Your Next Step?
Last updated
Was this helpful?

