Give each active laser project one editor and one local working copy. Share a completed, identified revision after checking it, and require the receiving operator to acknowledge that revision. A synchronized folder can distribute files, but it does not by itself tell two people whose changes should become the production version.
In a June 2026 LightBurn forum discussion about online drives, a user described backing up important files in Google Drive. The question establishes interest in online storage; it is not evidence that LightBurn damaged files or that a particular cloud service provides collaborative editing. The workflow below addresses ownership of shared production files.
Follow one job through two computers
Imagine the office computer changes a kit's label while the machine operator still has yesterday's copy open. Both filenames may look familiar. Saving both copies into one shared location can leave the team unsure which artwork was approved, even if every transfer completed successfully.
Assign an editor before changes begin. That person copies the released project into a local working folder and records the starting revision. The second operator can inspect a separate reference copy, but does not save competing edits over the active work.
When editing ends, save under a new revision identifier. Open that exact file, verify dimensions and the intended operations, and create a matching visual reference. Place the completed package in the shared release folder. The receiving person downloads or makes a local copy and checks that identifier against the job instructions before preparing output.
What the X1S Pro operator should receive
| File or record | Acceptance check before setup |
|---|---|
| Editable project | Opens locally and carries the released revision |
| Visual reference | Shows the same artwork, dimensions, and orientation |
| Job record | Identifies approved material, quantity, and machine configuration |
| Instruction document | Matches the kit version being manufactured |
| Change note | Names the person who released it and the change accepted |
Do not use a recent modification time as the only approval evidence. A rename, transfer, or later save can produce a fresh timestamp without a new customer decision. Keep older releases available in an archive so operators can establish what changed.
If two versions already exist
Stop preparing output from the disputed file. Preserve both copies with their original context and ask the designated owner to reconcile them. Compare the actual geometry, text, dimensions, and processing assignments; the larger file is not automatically the newer design.
If a mistake happened in an editor that remains open, Undo History within the same session may help inspect earlier edits where supported. It does not reconcile another computer's changes or replace an independently saved release.
For kits, release the assembly instructions alongside the parts. An apparently harmless label change can invalidate a diagram. Include that version in the new-builder instruction test so a successful assembly demonstrates that the files agree.
X1S Pro connection boundaries
The current TYVOK X1S Pro product page lists LightBurn and LaserGRBL workflow options. Confirm the supported software, profile, and output route for your installed configuration. Shared storage adds neither machine-side file locking nor remote operation permission. An approved project still needs the normal material, placement, and attended-operation checks.
Questions from shared workshops
Can both operators view the same released design?
Yes. Viewing reference copies is different from authoring competing changes. Make it clear which copy is for reference and who can create the next released revision. Verify the local copy before use rather than relying only on a cloud preview.
Is a synchronized folder enough backup?
Treat synchronization and recoverable backup as separate requirements. Check the storage provider's current version-history and retention behavior, keep a separate backup appropriate to your shop, and test restoration of a non-production file before depending on it.
