Cloud collaboration

Cloud projects let a team work from the same project files across Desktop and the browser. RunMat Server stores the project, its file history, and its membership.

Computation remains local by default for every collaborator. Team members can use different execution targets, so record the target and configuration when comparing numerical results.

Share a project

1. Open the cloud project.
2. Select Share project.
3. Add the collaborator or open the project team settings.
4. Choose access appropriate to their work.
5. Send the project link.

The Share action appears when the project and your role allow membership changes. Organization owners and administrators can also manage access from the organization team page.

A local folder must be moved to a cloud project before it can use RunMat sharing. Review the files being uploaded, especially datasets, generated output, and secrets.

Work on shared files

Desktop synchronizes saved changes to the cloud project. A teammate's saved changes appear as project updates on other connected clients.

Unsaved editor changes stay in the local buffer. When the same file changes in the cloud, Desktop asks you to compare or resolve the two versions before replacing your work. Coordinate ownership of heavily edited files and save cohesive changes frequently.

Use file history to inspect earlier versions of one file. Use a project snapshot before a broad refactor, dependency update, or multi-file migration so the team can review or restore the project as a unit.

Collaborate on a change

1. Confirm the project and branch or snapshot the team is using.
2. Agree on ownership for files under active development.
3. Make and save the source changes.
4. Run focused tests, then the project entrypoint or full suite.
5. Share the relevant run, notebook, or reported values with the change.
6. Review the file diff and create a project snapshot when appropriate.

Run records and notebooks help communicate results, while file history preserves the source that produced them.

Resolve access problems

When someone cannot open a project, check:

• that they are signed in to the intended account;
• the active organization in Desktop;
• their organization and project membership;
• the project link and visibility;
• whether an invitation or provisioning change has completed.

Removing access prevents future project requests from that identity. Copies already downloaded or exported remain outside the project.