Table of Contents

IFC Viewer in SharePoint FAQ

Data processing

Which usage and metadata does the SharePoint IFC web part process?

The SharePoint IFC web part processes the Azure backend metadata described in the architecture and data protection documentation (for example, tenant ID and anonymized usage information). No IFC or BCF content is sent to Flinker.

Where are the SPFx assets of the IFC Viewer for SharePoint hosted?

The SPFx assets of the IFC Viewer for SharePoint are hosted in the Microsoft 365 CDN of your tenant. At runtime, the viewer module is additionally loaded from a Flinker Azure CDN, as documented in the architecture and data protection section.

Can I view multiple IFC models at the same time?

Yes! You can load multiple models in the IFC Viewer for SharePoint by adding multiple IFC files from your SharePoint library.

  • See here how to add multiple files in the IFC SharePoint viewer: Click here.

Can I create a persistent federated model view for a SharePoint page?

Yes. An IFC Viewer for SharePoint web part configured with all relevant models acts as the persistent federated view - every user who opens the SharePoint page sees all models loaded automatically without re-selecting them.

For projects with many discipline models (for example, 30–35 separate IFC files), the folder link approach is recommended:

  1. Store all discipline IFC files in one SharePoint document library folder.
  2. Add the IFC Viewer web part to a SharePoint page.
  3. Open the web part settings and paste the direct folder path of that folder.
  4. Save and publish the page.

All models in the folder load automatically for every user who visits the page and has access to the folder. New IFC files added to the folder are picked up on the next page load without changing the web part configuration.

To share the federated view, share the SharePoint page URL. Anyone with read permission for the page and the folder will see the same model set.

Note

There is no separate "Save as federated view" action. The web part configuration on the SharePoint page is the persistent, shareable federated view. Files opened locally via the Open IFC button are visible only to the person who opened them and are not retained on page reload.

Can I open a local IFC file from my desktop in the IFC Viewer for SharePoint, and how does that differ from loading a file from SharePoint?

Yes - the IFC Viewer web part can open an IFC file directly from your local desktop. The file is loaded and processed entirely in your browser (client-side); nothing is uploaded to SharePoint or any external server. Only the user who opened it can see the model; it is not visible to other users visiting the same SharePoint page.

The shared use case works differently: you store the IFC file in a SharePoint document library and configure its URL - or a folder URL - as the source in the web part settings. Every user with permission to access the SharePoint page and the file then sees the same model. Any updates saved to the file in SharePoint are reflected in the viewer automatically. When a folder is configured as the source, the viewer loads all IFC files in that folder and picks up changes to any of those files without manual reconfiguration. This is the standard setup for a shared BIM coordination model in a Teams project channel or a SharePoint project site (SharePoint CDE).

Can you set which users can see the IFC model in SharePoint?

Yes. You can determine which users or user groups can see the 3D or IFC model by using SharePoint permissions (for the page and the IFC file) and Microsoft security groups. If you need additional protection workflows, you can also use ISO 19650 to restrict access and define who can edit the model.

Troubleshooting

The viewer opens but the screen only darkens and a close button appears - the viewer never fully loads. What should I do?

The viewer library is most likely missing from trusted script sources. A SharePoint admin must add https://viewer.flinker.app/ under SharePoint admin center > Advanced > Trusted script sources.

Follow the step-by-step instructions: Step 3 - Add the viewer library to trusted script sources.

Note

This step is required for the viewer to load. Without it, the viewer initializes but the script cannot be fetched, leaving only the darkened overlay and close button visible.

Updates

How often do I need to update the IFC Viewer for SharePoint, and how?

Update the IFC Viewer for SharePoint at least 1–2 times per year. Unlike other Flinker Microsoft 365 solutions, the IFC Viewer for SharePoint is an SPFx app that Flinker cannot update automatically - you must pull the update manually via the App Catalog.

Follow the step-by-step instructions: Upgrade IFC Viewer to the latest version.

Tip

Each upgrade delivers the latest features, security patches, and performance improvements. Only a SharePoint administrator can perform the upgrade.

Last updated on 2026-04-15
Raise issue