Project boxes · all pages

TEAMS AND ORGANISATIONS

Project boxes

Shared work parts with version history and conflict resolution — open to people from different workspaces.

A project is a shared space for ongoing work. It is not a workspace and not a context: membership is the only grant, and a project can include people from different workspaces. Its content is encrypted under a project-scoped key, so every member can read it and nobody outside the member list can.

Parts and versions

A project is made of parts — pricing, architecture, contract status, anything you name. Each part has a history of versions: who changed it, when, why, and what version it was based on. A version based on the current one becomes the new current version.

Conflicts

If two people start from the same version and both submit changes, the second one opens a conflict rather than overwriting the first. The current version stays untouched. conflict_list shows both sides; conflict_resolve settles it:

ResolutionMeans
keep_aKeep the current version; discard the pending one.
keep_bReplace the current version with the pending one.
mergeSupply a merged body; both sources are recorded.

Parallel work is never silently overwritten. Every action is in the project history.

Members

An owner adds and removes members and changes roles. Editors can add versions; viewers can read. Members may come from different workspaces — a project is its own access boundary.

In the console

Projects in the admin console lists your projects, lets you create and archive them, manage members, browse parts and versions, and resolve conflicts.

Docs version 1.3 · Something unclear or missing? Tell us.