Revision & Approval Workflow
Redirecting...
- Approval decisions recorded on the file itself, not in email threads.
- Released revisions locked, so manufacturing never builds the wrong one.
- Audit trail per file, useful for ISO, FDA, and customer reviews.
Trusted by SolidWorks engineering teams across industries
Built-in revision control for SolidWorks
Sibe is built specifically for SolidWorks teams. The native add-in keeps version tracking and releases inside the CAD environment engineers already work in.
- Check files out and in directly in SolidWorks. Sibe locks them to prevent overwrites.
- Every check-in creates a new version with a record of who changed what.
- Promote a final version to a formal revision when it's approved.
- Released revisions are locked, so manufacturing only sees the approved file.
Engineers keep their natural workflow in SolidWorks. Sibe handles revision history and release structure in the background.
Simple workflow states that match your process
Every file in Sibe lives in one of three states: In Progress, Pending Approval, or Released. Engineers iterate freely in In Progress. When a file is ready, they submit it for approval and add release notes. An owner reviews it, approves, and Sibe locks the released revision.
- Engineers submit files for approval directly from the web dashboard.
- Release notes are required at submission, so the reasoning is captured.
- Owners approve or send back for changes, every decision logged.
- On approval, Sibe assigns the next revision level and locks the file.
The same three states, applied consistently to every file, no custom workflows to set up, no admin overhead.
Approvals in the browser for non-CAD stakeholders
Most approvers don't use SolidWorks, they use email, browsers, and meetings. Sibe brings them into the workflow with a secure browser link. No SolidWorks licence. No install. No VPN.
- Send a secure link or QR code to managers, manufacturing, quality, or customers.
- Reviewers rotate, measure, and section the 3D model in any browser.
- Comments and mark-ups stay tied to the exact version they were made on.
- Approvals are recorded against the file, not buried in email threads.
Free unlimited web viewers on every plan, so the design view chain costs nothing extra.
Clear ownership, tasks, and audit trail
Approvals are only useful if you can see who decided what and why. Sibe records every state change, comment, and approval on the file so anyone can open a released revision and read the full story.
- Pin change requests as mark-ups directly on parts, subassemblies, or drawings.
- Every state change (In Progress → Pending Approval → Released) is recorded automatically.
- Reviewer comments and approval decisions stay attached to the version they refer to.
- A history log per file, useful for audits, ISO, and customer certifications.
Every approved revision has a clear story: who requested it, who approved it, and what changed.
Role-based permissions and safe access
Approvals work because not everyone has the same level of access. In Sibe, owners control approvals and releases, members work in SolidWorks and check files in and out, and external viewers see only what you share with them.
- Owners approve releases and manage workspace access.
- Members check files in and out of SolidWorks and submit for approval.
- External viewers open files in a browser through secure links, no Sibe account needed.
- Released revisions are locked and cannot be accidentally overwritten.
- Revoke any access in one click when a project closes.
Reviewers see what they need. Editors edit. The wrong person never overwrites the wrong file.
External partner and supplier approvals
Most products depend on suppliers, contract manufacturers, and external design partners. Sibe brings them into the same approval workflow without opening your full vault.
- Share controlled, IP‑protected views of assemblies and drawings with external stakeholders in the browser.
- Choose which files each supplier can see, your full vault stays private.
- Get supplier sign-off recorded against the version they reviewed.
- Stop sending STEP files and PDFs over email just to get an approval.
Suppliers see exactly the revision you want them to see, and you see exactly when they’ve reviewed it.
How a typical approval flow looks in Sibe
STAGE 1 — DESIGN (state: In Progress)
"Engineer works in SolidWorks, checks files in and out of Sibe, and iterates through versions while the file is In Progress."
STAGE 2 — SUBMIT FOR REVIEW (state: Pending Approval)
"When ready, the engineer submits the file for approval, adds release notes, and Sibe notifies the owner. A browser link can be shared with any non-CAD reviewers."
STAGE 3 — APPROVE & RELEASE (state: Released)
"The owner approves. Sibe locks the file, assigns the next revision (A, B, C…), and Released becomes the version manufacturing and suppliers see."
IP Protection Without Slowing Collaboration Down
Works for Everyone — Inside and Outside the Company
Sibe is designed for modern engineering teams, where the work doesn't stop at the company boundary. Whether you're co-developing with a partner, getting quotes from a supplier network, or walking a customer through a design review, the sharing experience is the same: fast, secure, and frictionless.
Internal engineers access the vault through the SolidWorks add-in or web app
External partners and customers access via browser link — no account required
No VPN. No IT ticket. No file sent over email.
"We're remote. The designer is in Philadelphia, our CTO is in Miami, and I'm in Austin. We needed a way to design, review, and release without everyone sitting in the same place — or even in the same software."
Alberto Lopez
Chief Executive Officer,
Sunfish
"Our SolidWorks files carry structured product data that people outside the CAD team regularly need to access. Bridging that gap was essential for our global growth."
Dean Pascasio
CAD Engineering Lead,
Nordair Systems
Enterprise-ready Security & Privacy
Everything in Sibe is designed to keep your work safe and secure.
Because your business is nobody else’s business.
SOC 2 Audited
Audited for Service Organization Controls (SOC 2 Type II) compliance.
Data Encryption & Backups
AES-256 encryption with daily backups and disaster recovery protocols.
Google Cloud Partner
Hosted on Google Cloud with data centers in Europe and the United States.
Frequently Asked Questions
Does Sibe work with my existing SolidWorks files?
Yes. Sibe connects to your existing SolidWorks projects through a native add-in. There is no migration, no file conversion, and no rebuild of your folder structure required. You connect your files and the revision workflow is live the same day.
Do approvers need a SolidWorks licence to review and sign off?
No. Anyone you share a link with opens the full 3D model in any browser, no SolidWorks installation, no licence. Paid collaborator seats unlock commenting and mark-ups directly on the design for those who need to leave structured feedback.
What happens to a file once it is released?
Released files are automatically locked in Sibe. They can be viewed and referenced by anyone with access, but they cannot be edited or overwritten. Any changes require a new revision cycle with its own review and approval.
Can I run approvals with external suppliers and contract manufacturers?
Yes. External partners join the review through a secure browser link, no account, no VPN, no SolidWorks licence. Web viewing is unlimited and free for as many partners as your project needs. Add a paid collaborator seat for partners who need to comment or add mark-ups. You control which files each partner sees, and whether they can download.
How does Sibe prevent two engineers from overwriting each other's work?
Sibe uses check-out / check-in directly from the SolidWorks add-in. When a file is checked out by one engineer, it is locked for editing by others. Everyone else can still view the latest checked-in version in read-only mode.
Can I see the full history of changes and approvals on a file?
Yes. Sibe maintains a log of every version, every state change, every reviewer comment, and every approval decision, all attached to the file itself. You can trace any released revision back to who requested it, who approved it, and what changed.
What are the workflow states in Sibe?
Sibe uses three clear states: In Progress, Pending Approval, and Released. Engineers iterate freely while a file is In Progress. When it's ready, they submit it for approval, the file moves to Pending Approval and the owner reviews it. Once approved, the file is Released, locked, and assigned the next revision level (A, B, C…).
Can I restrict who has the authority to approve a release?
Yes. Only owners can approve a file and move it to Released. Members and external reviewers can comment, mark up, and flag feedback, but the final release decision stays with the owners you designate.
Do I need servers or IT support to run approval workflows?
No. Sibe runs entirely on Google Cloud. There are no servers to set up or maintain, no VPN required for remote access, and no IT project to get started. Your approval workflow is live in under 20 minutes.
Book a free Demo with Ken to see Sibe in action
Ken Maren
Chief Solutions Architect
SolidWorks Expert with 30+ Years Experience
Thank you for requesting a demo.
Our Customer Success team will be in touch within one business day to arrange a suitable time.
Alternatively, please select a time slot directly from the calendar below.