Web Analytics Made Easy - Statcounter

Check Out, Change, Check In: SolidWorks Version Control Without a Server

Ken Maren
PUBLISHED
November 16, 2026
LAST UPDATED
November 17, 2026
READ TIME
4 min read

Working in SOLIDWORKS® 3D CAD, you can keep one assembly under control from check-out to release without a server, a VPN or an admin. Ken runs the whole loop on a real assembly in 17 minutes.

Check-out is a lock, not a download

You check a part out from the Vault tab in the add-in, directly in SolidWorks. While you hold it, nobody else can edit it. They can still open it, look at it and reference it from their own assemblies. The file is yours until you check it back in.

That distinction carries the rest of the loop. A lock gives one person exclusive access and shows everyone else who holds it. On a network drive or a synced folder, access is shared by default, so two people can have the same part open without either of them knowing.

If you would rather watch than read, the 17-minute webinar runs this same loop on a real assembly, with no slides.

A version is every check-in. A revision is what you release.

When you check the part back in you add a short comment, and a new version is written. The version list sits beside the file: v1, v2, v3, who changed it, when, and what they said they changed. You can open an older version directly in SolidWorks, look at it, and carry on from the current one.

Keeping those two ideas apart matters more than it sounds. Versions are cheap and there are many of them, one per check-in, and they answer what somebody changed on Tuesday. Revisions are few and deliberate, cut when a design is released, and they are what manufacturing and your auditor work from. Sibe tracks both, and the audit trail runs through both.

Why assemblies break on a shared drive

You open the assembly and every reference resolves, including after somebody has reorganized a folder. Sibe tracks how your files relate to each other, not only where they sit.

That is worth understanding before you compare options, because an assembly is a set of relationships rather than a set of files in a folder. Rename a folder, move a part, or sync the same subassembly twice, and the relationships are what break, which is why the symptom is a missing reference rather than a missing file. File storage tracks paths. Reference handling is the specific job you are shopping for, and it is the reason most teams move off a shared drive even when nothing else is wrong.

Your files still live on your machine. Sibe mirrors your folder structure in a local cache folder, so the layout looks similar to the one your team uses now. There is nothing new for an engineer to learn about where things are.

Four questions you stop asking people

You can answer these from the dashboard, without messaging anyone:

  • Who has a part checked out right now
  • Which version is current, and what changed in the last one
  • Where a part is used, across every assembly that references it
  • What state a file is in: in progress, in review, or released

Worth timing on your own team before you change anything. Most of the time lost to file admin goes on questions like these, not on the CAD work itself.

Reviewers do not need a SolidWorks seat

Send a free Visitor Link or a QR code. The reviewer opens the model in a browser, on a laptop or a phone, with no account and nothing to install. They can rotate it, measure it and mark it up.

Where the markup lands is what changes how reviews go. Type an at sign, pick who should see it, write the note on the model, and the owner gets an email. The thread stays with the part, so six weeks later the reason for a change is still next to the change rather than in somebody's inbox. There is more on that on the design reviews page.

Release is a gate, not an email

When the design is ready you pick your approvers and mark which of them are required. You can notify others without blocking on them. The file moves to Released only once every required approver has signed.

Until then it sits in review: visible to everyone, editable by nobody. If something comes back, you transition the file to In Progress and the loop starts again. The gate sits on the file, so it does not depend on anyone remembering to hold it.

When a shared drive is still fine

If one engineer owns every file, revisions are rare, and nobody outside the CAD team needs to see the model, a tidy folder structure and a naming rule will hold. Version control starts to pay when a second person can open the same part, when you have to prove what shipped, or when reviewers sit outside SolidWorks.

Most teams reach the second engineer and the first external review at about the same time. That is the point worth planning for, rather than the week a reference breaks.

What it takes to set up

A workspace is live in under 20 minutes. Each engineer installs the add-in: close SolidWorks, run the installer, open SolidWorks again, and sign in with a Sibe account. Installation takes 2 minutes. The add-in works with SolidWorks 2021 through 2027.

There is no server to buy, no VPN to set up and no admin to appoint. That is the practical difference between a Cloud PDM and an on-premise one: the infrastructure is somebody else's to run.

Watch the loop end to end

The 17-minute webinar runs everything above on one real assembly, start to finish, with no slides. It is split into 14 chapters, so you can go straight to the part you are evaluating: check out, change, check in at 8:49, and the release and approval workflow at 12:00. There is no form and no sign-up.

If you want the version-control mechanics written up on their own, without the walkthrough, that is on the version control page.

Book a free Demo with Ken to see Sibe in action

Book a Live Demo with our product Expert
Ken Maren, SolidWorks Admin with 30+ years experience, Chief Solutions Architect at Sibe, ready to demo Sibe

Ken Maren

Chief Solutions Architect

SolidWorks Expert with 30+ Years Experience

Redirecting...

Oops! Something went wrong while submitting the form.

Latest Articles

GVSU Laker Racing, off OneDrive. Sibe sponsorship
GVSU Laker Racing: Moving a Formula SAE Car Off OneDrive
Read More
Article
September 30, 2026
GVSU Laker Racing: Moving a Formula SAE Car Off OneDrive
GrabCAD Workbench shutdown and what SolidWorks teams use now
GrabCAD Workbench Is Discontinued: What Happened and What Teams Use Now
Read More
Article
September 27, 2026
GrabCAD Workbench Is Discontinued: What Happened and What Teams Use Now
Embed SolidWorks designs anywhere with Sibe
Embed 3D Models From SolidWorks on Any Web Page, Live and Interactive
Read More
Sibe How-to
September 22, 2026
Embed 3D Models From SolidWorks on Any Web Page, Live and Interactive
IZTECH Racing: five subteams, one car. Sibe sponsorship
IZTECH Racing: Five Subteams, One Car, Two Podiums
Read More
Article
September 27, 2026
IZTECH Racing: Five Subteams, One Car, Two Podiums