Teams and roles (coming soon)
A preview of team workspaces: roles, a pooled credit allowance, a team library, reviews and enterprise controls. Not available yet, but here is what to expect and how to prepare.
Solid Vibes today is built for individual makers and professionals. Teams are next.
What is planned for the Team plan
| Area | Plan |
|---|---|
| Seats | Per-user pricing (placeholder: about $29 per user per month) |
| AI credits | A pooled allowance across the team (placeholder: 4,000 per user per month) |
| Things | Unlimited, within fair use |
| Storage | A large pooled amount (placeholder: 1 TB) |
| Collaboration | Real-time multiplayer with live cursors and selections |
| History | Everything in Pro, plus review requests |
| Library | A team-only library of approved Things and parts |
| Security | Admin controls and audit logs (sign-ins, shares, exports, permission changes) |
Roles
Team workspaces use five roles:
| Role | Can |
|---|---|
| Owner | Everything, including billing and deleting the workspace |
| Admin | Manage members, roles and workspace settings |
| Editor | Create and edit projects, commit, merge |
| Reviewer | Comment and approve review requests |
| Viewer | View and export, if allowed |
On top of roles, you will be able to set per-project overrides, and use share links with view, comment, edit or fork permission, expiry and password.
Planned ways of working
Review requests
A review request is a "pull request" for hardware. An engineer branches, proposes a change, and a reviewer sees the visual diff and parameter changelog, adds 3D comments pinned to faces and edges, and approves or asks for changes.
Team library
A shared catalog of Things your company has approved: house-standard brackets, enclosures, fastener sets. Engineers reuse them rather than reinventing parts, and updates flow to everyone who uses them.
Release tags
Release tags freeze geometry, drawings and the Make list together, so "v1.0 sent to factory" can be reproduced exactly. This already exists on Pro, and becomes central to team workflows.
Enterprise
For larger organizations, the plan is to add:
- Single sign-on (SAML) and SCIM provisioning,
- Domain capture and enforced MFA,
- Data residency options and a service-level agreement,
- a private organization marketplace with approval workflows,
- approvals in history,
- custom limits and pricing.
What you can do today to prepare
- Adopt the habits that scale. Use parameters with clear names, groups, and descriptions. Write design intent for rules everyone should respect.
- Use branches and release tags (on plans that include them) so history is meaningful to others.
- Keep Things focused, one product or subsystem each, so they are easy to review and reuse.
- Agree on conventions: naming for Things and branches, standard materials and printers, tolerance values (a team-wide
fit_clearance). - Build a set of reusable Things (brackets, enclosures, hinges) that could seed a team library.
- Turn on strong sign-in for everyone: passkeys and an authenticator app.
- Decide who would own what: owner, admins, and who would review.
Using Solid Vibes with a team right now
You can already collaborate in simpler ways:
- Share links to view, comment (Maker and above) or edit (Pro) a Thing.
- Exports (STEP, STL, 3MF, PDF) for colleagues who use other tools.
- Forking and release tags for handoffs.
- The mobile viewer for quick reviews on a phone.
See Workspaces, projects and sharing.
Stay informed
Plans and launch details are announced in the changelog, which includes short videos. If your organization wants to be considered for early access, tell us through the help center feedback or support.
Try it
Draw up your team's conventions as a short list: how you name Things, what your default clearance is, which printers and materials you standardize on. Then ask the agent to apply them:
Apply these team standards to this Thing: a fit_clearance parameter of 0.25 mm, walls never thinner than 1.6 mm, and all screws M3 with heat-set inserts. Tell me what you had to change.
Did this help?
Keep reading
Account and billing
Workspaces, projects and sharing
How your work is organized (workspaces, projects, Things, pieces), how the trash works, and how to share a Thing with a link without giving away more than you mean to.
Beginner4 min readAccount and billing
Plans and limits
What each plan includes: Things, private Things, storage, credits, exports and features. And what happens when you reach a limit (spoiler: nothing is deleted or locked).
Beginner4 min readAccount and billing
Account security: passkeys, MFA and sessions
Sign in the safest way, set up a passkey and an authenticator app, manage your devices, and understand how Solid Vibes protects your data.
Beginner4 min read