Projects are optional, shared workspaces in the ClashWise web app. A project groups related clash sets together and makes certain resources — tags, matrices, and saved filters — visible to every member of the project, so a coordination team can work from the same library instead of recreating it person by person.
Projects are strictly opt-in. If you never create one, nothing changes: your clash sets keep working exactly as they do today, owned by you and visible to you.
What a project does
A project is a container with:
- Clash sets — the published sets you and your teammates have attached to the project.
- A shared tag library — every tag used across the project's clash sets, gathered in one place.
- Shared matrices — clash matrices that members have shared with the project. Members gain read access so they can apply a shared matrix to their sets; the matrix always remains owned by the person who created it.
- Saved filters — filtered views created inside the project are visible to every member.
- Members and roles — each project has its own member list with two roles, Owner and Member.
Why use a project
Use a project when more than one person coordinates the same job:
- Everyone sees the same clash sets in one place, instead of sets living only under individual accounts.
- Tags stay consistent across the team, because everyone draws from (and adds to) the same shared tag library.
- One well-built clash matrix can be applied by the whole team — members get read access to matrices shared with the project.
- Saved filters built by one person are available to everyone, so a "structural vs. mechanical, unresolved only" view doesn't have to be rebuilt by each teammate.
If you work alone, or your clash sets don't need to be shared, you can skip projects entirely.
Who can use projects
- You need a ClashWise account and must be signed in to the web app. Projects live on the web — there is nothing to configure in the Navisworks plug-in.
- Creating a project requires the Business plan (during open-beta periods project creation is available to all accounts). The person who creates it becomes its first Owner. Once a project exists, invited members work in it regardless of who holds the Business subscription.
- Within a project, Owners manage members, settings, tags, and deletion; Members work with the shared content. The details are covered in the Managing a Project article.
- Note that project roles are separate from organization roles. Being an organization Admin does not automatically make you a project Owner, and vice versa.
Where to find projects
Open Projects in the ClashWise web app at https://clashwise.ai/my/projects. The page lists every project you belong to as a card showing the project name, your role tag (OWNER or MEMBER), a description, and counts for CLASH SETS, MEMBERS, and when it was last UPDATED. Clicking a card opens the project hub.
If you haven't created or joined any projects yet, the page shows "No projects." with a reminder that projects are optional: you can create one to organize clash sets into a shared workspace, or keep using clash sets on their own.
How clash sets relate to projects
- Clash sets are only ever created by publishing from the Navisworks plug-in — a project does not create clash sets.
- A clash set starts out as a personal, per-user set. You attach it to a project afterwards from the Clash sets page: open the set's menu and choose Move to project… (you can later use Change project… or Remove from project).
- A clash set can belong to at most one project at a time.
- On the Clash sets page, sets that belong to a project show a project chip that links straight to the project.
- If a project is ever deleted, its clash sets are not lost — they simply revert to being per-user sets under the people who created them.
What is not shared
- Matrices stay owned by their creator. Sharing a matrix with a project gives other members read access so they can apply it — they cannot edit or delete someone else's matrix, and the creator can remove it from the project at any time.
- Clash sets keep their creator. Attaching a set to a project doesn't transfer ownership; deleting the project returns owned sets to their creators.
- Your other clash sets remain yours. Anything you haven't attached to a project stays personal.
Tips
- Create one project per coordination job or client, and name it distinctively — ClashWise warns you if you try to reuse a name you already have.
- Attach clash sets to the project as soon as they're published, so tags and saved filters accumulate in the shared library from day one.
- Agree on tag names early. Project Owners can rename or delete tags across every clash in the project, which is the easiest way to clean up inconsistent tagging later.
FAQs
Do I need a project to use ClashWise? No. Projects are entirely optional. Clash sets, matrices, analysis, the 3D viewer, and coordination sessions all work without a project.
Can a clash set be in two projects? No. A set belongs to at most one project. Sharing a matrix that is already in another project will move it to the new project (the dialog flags this as IN ANOTHER PROJECT).
What happens to my clash sets if the project is deleted? Clash sets you own revert to being your personal sets. Other members lose the access they had through the project.
Is a project the same as an organization? No. Your organization manages your subscription, seats, and billing (see the Your Organization article). A project is a lighter-weight workspace for grouping clash sets and sharing tags, matrices, and saved filters with a specific team.
Related topics
- Managing a Project — creating a project, the project hub tabs, inviting members, and deleting a project.
- Your Organization — seats, roles, billing, and organization settings.
- Clash Sets on the Web — publishing, renaming, and moving clash sets.
- Clash Matrix — creating and applying matrices.