How projects keep files, decisions and teamwork together

A project is useful when work must survive beyond one conversation and has a defined outcome, source material, status and next action. A standalone discussion or temporary attachment does not automatically become a project record.

• Create a project for a durable piece of work with a clear purpose.
• Keep casual questions and temporary exchanges in their conversation scope.
• Bind a conversation to one project only when that project context is required.

The dossier points people and the assistant to the current state without trying to replace detailed invoices, correspondence, calculations or reports.

• Purpose, status, due date, assignment and next action where relevant.
• Important sourced facts, open questions and conflicting information.
• Related conversations and a file index for evidence and deliverables.
• Detailed records remain in their linked files or authoritative connected systems.

An incoming file is archived in the current user's conversation scope. It becomes a durable project record only after an explicit promotion or copy into an authorised project.

The creator becomes the project owner and can grant or revoke access for active members of the same business. The same access decision governs project discovery, files, conversation binding and project work.

• Projects without a valid ownership record fail closed.
• Sharing a project does not reveal the owner's other conversations or private files.
• Private access records cannot be changed through ordinary workspace file editing.
• Time-limited delivery links are renewed only after authorisation is checked again.

Research, calculations, documents and approved communications can build on one another through the same project workspace. Derived work keeps enough metadata to identify its purpose, source material and relationship to the final outcome.

• Original evidence is normally preserved rather than overwritten by a later result.
• Temporary working files remain distinct from durable evidence and customer deliverables.
• Final deliverables are persisted before ValueSpace reports the work as complete.
• External delivery can still require a separate approval.

ValueSpace uses the authorised project workspace as the durable boundary for substantial work and team collaboration.

• Each project has a concise dossier with current status, sourced facts, open questions, files and next action.
• A conversation attachment remains private until it is explicitly promoted into an authorised project.
• The project owner can grant or revoke access for active members of the same tenant.
• Authorised colleagues can continue the same project without receiving access to unrelated private material.
• Generated deliverables are persisted before completion is reported.
• Artifacts retain purpose and source relationships so they can support verification and later work.

Learn how multi-step project work reaches verified completion and how ValueSpace already works with business documents and files.