Collaboration and project comments

Meratyn keeps collaboration local and portable. There is no hosted live session relay, governed collaboration service, or hosted activity log.

Share a project snapshot

Use Project → Share to create a redacted project snapshot, or save the .meratyn.json file and exchange it through a channel you control. A redacted copy removes service tokens, environment variables, provider keys, signed URLs, and other credential-shaped values. Reopen the file with Project → Open; each person works on their own local session and can send back a new snapshot.

The portable file is the collaboration boundary. It contains the project document, layer definitions, styles, map view, and any comments authored in the project. It does not provide shared presence, cursors, chat, participant roles, or remote synchronization.

Map-anchored comments

The Comments panel is a local project tool. Add a comment at the current map center, reply, resolve, delete, or select its marker to return to the location. Comments and replies travel with the project document, so a redacted snapshot can carry the review context without contacting a collaboration service.

Comment authors are local labels, not authenticated identities. Do not use the panel as an access-control or audit mechanism; use your organisation’s approved file-sharing and review process for those requirements.

Offline and embedded use

The same snapshot workflow works in the browser, desktop application, notebook embed, and exported HTML where project I/O is available. Remote data sources still follow their own network and credential requirements when each local session opens them.