pencil, pencils, black pencils, black, gray, closeup, eraser, white eraser, work, study, desk, gray work, gray study, gray desk, gray studying, pencil, pencils, eraser, eraser, eraser, eraser, eraser
Photo by kaboompics on Pixabay

Documents

Part of Business diagramming software: Visio, Lucidchart and Miro

Testing shared editing on a complex diagram

Use a complex-diagram scenario to assess simultaneous edits, conflicts, comments, permissions and recovery.

Assign several people changes to one demanding diagram, then check the result. A shared link only shows people can open the file. It does not show how simultaneous changes, comments or recovery work.

Prepare one controlled diagram

Use a fictional process with several lanes, a decision, a return loop and a second page or frame. Keep an untouched source.

Give one person a step to change, another a connected group to move and a reviewer a decision to comment on. Have two editors attempt to change the same label. Record the intended final diagram before starting.

Use the account types and devices staff would use. Include an ordinary editor and a commenter. If guests will participate, test their proposed access; do not assume a team-member account behaves the same way.

MomentEvidence to collect
EntryWho can view, comment and edit?
Separate editsDo changes appear without lost connectors or labels?
Same-object conflictIs a change blocked, overwritten, retried or handed off?
ReviewDoes the comment remain attached to the intended step after shapes move?
RecoveryCan the team identify and restore an earlier state in the proposed plan?
HandoffCan a colleague outside the session explain the final route?

Know what each product means by collaboration

Visio: Microsoft's web app supports co-authoring. Simultaneous editors must use the same app type; browser and desktop editing cannot be mixed on one file at the same time.

Visio desktop co-authoring guidance specifies OneDrive for Business or SharePoint Online and Visio Plan 2 for Windows authors. Non-conflicting updates merge automatically. Include a contested edit in the test and record what happens.

Lucidchart: Test the sharing, comment and recovery controls exposed to the account you are evaluating. Record what each collaborator can do and whether a previous state can be restored.

Miro: Check the access choices and board limits shown for the test account. Before using sensitive content, verify whether invited collaborators can view, comment, edit or change sharing settings.

Camunda Web Modeler: Access to files and folders is defined at project level. Project roles include Project Admin, Editor, Commenter and Viewer. Commenters can view diagrams and properties and leave comments; viewers can only view diagrams. Test the assigned role boundaries and record whether each person can perform only their intended actions.

Collaboration features across diagram tools

  • VisioCo-authoring via OneDrive for Business or SharePoint Online. Desktop and browser edits cannot be mixed. Conflicting changes merge automatically if non-conflicting; contested edits require manual resolution.
  • LucidchartSupports sharing, commenting, and revision history. Previous states can be restored. Access roles include editor, commenter, and viewer with defined permissions.
  • MiroBoard access rights include view, comment, edit, and change sharing settings. Free plan limits apply. Invited collaborators' capabilities depend on assigned roles.
  • Camunda Web ModelerProject-level roles: Admin, Editor, Commenter, Viewer. Commenters can view and comment; viewers can only view. Permissions are strictly enforced at the project level.

Review the result

Close the editing views and ask a fresh reader to trace the process. Check the contested label, moved connectors and review comment. If a change was lost or blocked, record the message and recovery action. Retest the affected step after changing settings.

Keep the source version, plan, permissions and expected outcome with the observation. A successful rehearsal in one account does not establish performance for every diagram size or network condition. Treat the rehearsal as a pass only if each assigned role can complete its intended action, the contested edit has a clear outcome, and a reviewer can recover from any unwanted change.

More from Documents