Share the project. Choose what goes with it.
Give clients and project stakeholders access to the BIM project while controlling whether they can also reach the original IFC or Revit files.
Sharing a project view and handing over the source file are two different decisions. A client may need to inspect the model and its properties without receiving the authored IFC or Revit file.
The xeoVision framework includes application workflows that separate project visibility from source-file access. xeokit SDK supplies the browser visualization; the deployed application controls access for the intended audience. Agree authentication, storage and sharing rules for the environment in which your solution runs.
It is a control over file access, not a rights-management system — anything visible on screen can still be captured.
See how to embed a project view in a portal, or review the deployment options for your data boundary.
How it works
- 01 Choose who should be able to view the project.
- 02 Set access to original source files for the intended audience.
- 03 Share the viewing experience with the permissions you choose.
Can you share a BIM model without sharing the source file?
Yes. Project visibility and source-file access are separate decisions in the application workflows, so a reviewer can be given a project view without also being given the original IFC or Revit file to download.
Does this stop people copying the model?
No. It is a control over file access, not a rights-management system. Anything visible on screen can still be captured, so treat it as a way to decide who reaches the source files rather than as protection against a determined recipient.
Who decides what a reviewer can see?
You do, as part of the project access you configure. The decision about the view and the decision about the underlying files are made separately, so each can be set to suit the audience for that particular review.
