Compare versions and collaborate on a project

The result you can request

The assistant finds saved versions, compares their data and results, then can prepare a restoration. Comments and sharing help track points to review with authorized people.

Required access: Read; edit and owner role depending on the action.

Information to supply

Choose the project, versions or relevant section. For sharing, provide the person’s email address and the desired role: read or edit.

1. Compare changes and results between versions.
2. Review comments and existing access.
3. Confirm restoration and sharing changes separately.

Requests to copy into your assistant

Enable open-bp in the conversation and choose the relevant project. Review modification requests before saving anything.

Compare the two versions I will choose for this project. Summarize changes to assumptions, sources and results. Do not restore a version without my confirmation.

Prepare read-only access to this project for the person whose email address I will supply. Check permissions and show me the role before creating the invitation.

Checks and limitations

Restoration creates a new version and preserves history. Saving checks the expected version. Sharing requires owner permissions and plan capacity; accepting an invitation verifies the email address.

Permissions, quotas and versions are checked by the server. For an external AI client, keep confirmation required for every action that saves, shares or changes your account.

Corresponding MCP tools

These names let an agent find operations in the catalogue. The list available to your connection depends on its granted permissions.

• revisions_list
• revision_compare
• revision_restore
• comments_list
• comment_add
• shares_list
• share_invite
• share_revoke