Skip to content

Collaboration overview

Every prop in Prophouse has a full version history, and your team works on it together through a small set of tools: an exclusive check-out so two people don’t edit the same prop at once, reviews that record who approved which version, comments and markup for feedback, and an inbox that tells you when something needs your attention.

A prop you see in the library is backed by a chain of immutable versions. Pushing changed bytes adds a new version, and the prop’s current version moves to it. Nothing is overwritten: you can open the version history at any time and restore an older one.

Most collaboration features attach to a specific version rather than to the prop as a whole:

  • A review decision belongs to one version. Pushing a new version resets the prop’s badge to Draft, and restoring an approved version brings its Approved badge back.
  • A comment can be about the whole asset or pinned to the current version.
  • Markup is drawn on one exact preview image or 3D preview, so it never drifts when a preview is regenerated.

A check-out lock, by contrast, covers the prop’s whole version history: while you hold it, other people’s pushes of new versions are held back and they can’t restore an earlier version.

Task Web library and desktop app Unreal plugin AI agents (MCP)
See version history, restore Yes No get_version_history, restore_version
Check out and release Yes Yes (catalog browser) checkout_prop, release_checkout
Check in a new version Desktop app only Yes (Push to Prophouse…) checkin_prop
Request and respond to reviews Yes Shows review state and decisions Review tools
Comment, mention, react, mark up Yes No add_comment, resolve_comment
Inbox and watching Yes No get_notifications, watch_prop

The desktop app runs the same library interface as the web app, plus local features such as the Checkouts and Conflicts pages and native notifications. Collaboration state lives on the server, so check-out, release and review actions need a connection.

For agents, every workflow on these pages has an MCP tool. See the tool reference.