Work with a team
These instructions are reviewed against the app source. Final-installer walkthroughs are still pending. Check platform availability and requirements before installing. Windows is an updates list, outside the 1,000 beta places.
MODO supports shared reviews, comments and a live canvas through a configured team service. This is separate from both a local project and a personal cloud history.
The implementation provides team sizes of 2, 5 and 10 members and role checks. These are capacity tiers, not a published subscription price or an included hosted service.
Connect to a service
Open File → Team & comments…. For remote use, choose HTTPS team service and enter the endpoint and personal access key supplied by its operator.
An operator must run and maintain the service, HTTPS, storage and backups. A local test service does not give remote teammates a reachable address. Never send the owner's key as a member invitation.
Share a review
- Choose the page and frame you want reviewed.
- Review the sharing description and confirm the review.
- Open the shared review and invite the intended members through the configured service.
- Add comments to the snapshot and discuss them with the team.
A review sends a PNG snapshot and layer names. It does not upload the full editable project or CMS drafts. Comments belong to that review revision; changing the local canvas does not silently move them onto a new screenshot.
Share an editable canvas
- From the team dialog, inspect the full-project sharing description.
- Confirm sharing the complete project, including assets and CMS drafts.
- Open the shared canvas and have authorized members join.
- Verify a small edit and shared cursor before starting substantial work.
Owners and editors can edit. Commenters and viewers cannot edit the document. Membership limits count people rather than browser tabs.
The shared project is a separate authoritative copy. Your original local project does not continuously synchronize with it. Download .modo from the shared canvas to bring the shared work back to a local project.
Handle connectivity and conflicts
Live editing requires a connection to the service. When offline, the shared canvas becomes read-only rather than accepting an unlimited offline editing branch.
Revisions protect against conflicting changes. A rejected edit needs review against the latest state. If an edit's outcome is uncertain after losing connection, reconnect and resolve it before discarding local pending work. Keep the tab and its data intact while resolving that state.
Local publish credentials, filesystem access and the local MCP daemon are not exposed through the shared canvas. Use a downloaded local project for those workflows.
See personal cloud versions and local saving.
Need a correction? Tell us