Table of Contents

IFC Viewer in Microsoft Teams FAQ

Setup and installation

How can I open an IFC file inside Microsoft Teams?

Microsoft Teams does not support IFC files by default. Install Flinker's IFC Viewer app from the Microsoft Teams app store, then add it to a chat or channel. For setup instructions, see IFC Viewer in Microsoft Teams - Quick Guide.

Can the IFC Viewer also be added as a tab in Microsoft Teams?

Yes. Add IFC Viewer for Microsoft Teams as a Teams tab when your organization allows apps from the Microsoft Teams app store. If app installation is blocked, contact your IT administrator.

How can I embed the IFC Viewer in Microsoft Teams if my organization does not allow adding apps from the App Store?

You can add the IFC Viewer as a website tab. Add a new Teams tab and enter https://viewer.flinker.app.

What advantages do I have when I use the official Microsoft Teams app instead of embedding the IFC Viewer as a URL in a Microsoft Teams tab?

When you embed the IFC Viewer as a website URL, users can load local files for their own session only. Other members of the channel or chat do not see those local files.

With the IFC Viewer for Microsoft Teams app, configure IFC files or folders from SharePoint or Teams. Users with the required SharePoint permissions see the same shared model when they open the tab.

Is it necessary to choose which chat or team I should set up the IFC Viewer?

Yes. The IFC Viewer runs as a Teams tab and must be added to a chat or channel.

Yes. Add separate IFC Viewer tabs to multiple teams or chats.

Get the file link from SharePoint or Teams:

  • Open the SharePoint or Teams Files tab.
  • Right-click the IFC file and select Copy link.
  • Paste the link into the IFC Viewer setup screen.

What if my file is stored on OneDrive or an external drive?

  • If the file is in OneDrive, copy the SharePoint link from OneDrive.
  • If the file is on an external drive, upload it to SharePoint or Teams first.

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

Yes - the IFC Viewer 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 you can see that model. Other members of the channel or chat cannot see it, and the file is not retained when the tab is closed or reopened.

The shared use case works differently: you store the IFC file in SharePoint or Teams and configure its URL - or a folder URL - in the tab settings. Every channel member with the appropriate SharePoint permissions then sees the same model. Any file updates saved to 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 coordination model in a Teams project channel or a SharePoint project site (SharePoint CDE).

Will everyone in my selected chats or teams also see every file I uploaded?

Only files linked in the IFC Viewer tab settings are visible to other team members. Files opened with Open IFC are local to the current user session and are not saved to the shared tab configuration.

To restrict access, update SharePoint file or folder permissions, or use ISO 19650.

Can I remove or change the files that are automatically opening whenever the tab is opened?

Yes. Open the Teams tab settings and remove or replace the configured file or folder links.

Can I set some files to open automatically but not others?

No, all files added in the Teams tab settings dialog are loaded automatically. You can, however, remove files later if you don’t want them to open by default.

What happens if I forget to upload files during setup?

Open the Teams tab settings and add the file links later. You do not need to recreate the tab.

Can I view multiple IFC models at the same time?

Yes. You can load multiple IFC models in the IFC Viewer for Microsoft Teams by adding multiple IFC file links in the tab setup, or by adding a folder link that contains multiple IFC and BCF files.

  • Setup guide (add multiple files in the tab): Click here.

How do I load only specific IFC files, not all files in a folder?

The IFC Viewer loads all IFC files found in the folder path configured in the tab settings. To load only specific files, use a more specific subfolder path that contains only the files you want to load.

Can I have multiple IFC Viewer tabs with different folders configured?

Yes. Add multiple IFC Viewer tabs to a Teams channel and configure each tab with a different folder path. This lets teams or projects keep separate model views.

Can I create a persistent federated model view for a project with many discipline models?

Yes. An IFC Viewer for Microsoft Teams tab configured with all relevant models acts as the persistent federated view - no re-selection is needed when the tab is reopened.

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 folder.
  2. Add a new IFC Viewer tab to the Teams channel.
  3. In the tab settings, paste the direct folder path of that SharePoint folder (not a sharing link).
  4. Save the tab.

Every team member who opens the tab sees all models loaded automatically. Any new IFC file added to the folder is picked up the next time the tab is opened, without reconfiguring the tab.

To share the federated view with colleagues, right-click the tab and select Copy link to tab. Anyone with the required SharePoint permissions for the folder will see the same model set.

Note

There is no separate "Save as federated view" action. The tab configuration itself is the persistent, shareable federated view. Colleagues who open locally loaded files via the Open IFC button see those files only for themselves; those files are not part of the shared tab configuration.

Can I set a specific BCF issue or clash to open by default in a Teams tab?

Yes. Open the Teams tab settings and paste the topic GUID into Set your default view (optional). After you save the tab, the viewer opens that BCF topic automatically each time the tab is opened.

Yes. Select the BCF topic in the IFC Viewer for Microsoft Teams and click the Share button in the upper-right corner. The generated Teams deep link opens the same tab with that topic selected, so the saved BCF issue context is shown again for the recipient.

Permissions and security

Which permissions need to be granted with the setup?

You need to grant read permissions so the IFC Viewer can access IFC and BCF files stored in SharePoint or Teams. If you cannot grant these permissions, you can still load local files from your desktop, but only you will see them. If you want to save BCF files back to SharePoint or sync BCF topics to Microsoft Lists, the app will also request write permissions at that point.

Can IFC Viewer edit or delete my files, or is it just viewing them?

By default, the app reads files to display model and BCF data. It writes only when you use save features such as Save to Teams/SharePoint or Microsoft Lists synchronization, and those actions require additional write permissions. The app does not delete files automatically.

Why does the app need permissions?

The IFC Viewer needs permission to read IFC and BCF files stored in your company's SharePoint and Teams so it can load them directly into the tab. If you use save features for BCF files or Microsoft Lists integration, the app also needs write permissions for those actions.

For authentication purposes, the user's email address and Microsoft tenant ID are transmitted to Flinker. No IFC/BCF file content or other personal data is shared externally. All file processing happens client-side within your Microsoft 365 tenant.

Does the IFC Viewer store my files somewhere?

No. Your files stay in your Microsoft 365 tenant and SharePoint. The app does not upload IFC or BCF files to an external file store.

Is my data secure when using the IFC Viewer?

Yes. Your IFC and BCF files are never uploaded or processed outside your Microsoft 365 tenant - all file processing happens client-side in the browser within your organization's SharePoint and Teams environment.

For authentication purposes, the user's email address and Microsoft tenant ID are transmitted to Flinker. No other personal data or file content is shared. This is consistent with the Microsoft App Compliance certification for IFC Viewer for Microsoft Teams.

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

Yes. Use Microsoft security groups, SharePoint groups, or ISO 19650 to control who can access the IFC file or folder. Use SharePoint permissions to control read or edit access.

What specific Microsoft Graph permissions does the IFC Viewer request, and what is their scope?

When you click "Connect", the IFC Viewer requests the following permissions via Microsoft Graph:

Permission Type Purpose
Files.Read.All Delegated Read IFC/BCF files from SharePoint and Teams on behalf of the signed-in user
User.Read Delegated Sign in and read the user's basic profile

Both are delegated permissions - the app only acts on behalf of the signed-in user, never autonomously or in the background.

For authentication purposes, the user's email address and Microsoft tenant ID are transmitted to Flinker. No IFC/BCF file content or other personal data is shared.

If your organization requires admin approval, your IT admin can grant consent directly using this link: Grant Admin Consent

You can also review the full Microsoft App Compliance certification: Microsoft App Compliance – IFC Viewer for Microsoft Teams

Are Files.Read.All and User.Read the only Microsoft Graph permissions requested for the initial setup?

Yes. Files.Read.All is used to read IFC/BCF files from SharePoint/Teams on behalf of the signed-in user, and User.Read is used for sign-in and basic profile access. We do not require any additional Microsoft Graph permissions for this setup. If additional Graph permissions were ever needed in the future, those would indeed require separate consent/approval.

Which write permissions are requested, and when?

Write permissions are only requested when you explicitly use save features - they are not part of the initial setup. The following write permissions may be requested depending on the features you use:

Permission Type Triggered by
Files.ReadWrite.All Delegated Saving BCF files back to SharePoint or Teams
Sites.ReadWrite.All Delegated Microsoft Lists synchronization for BCF topics

The app never writes to your files without an explicit save action initiated by the user.

Tab management and visibility

Can I control who can modify the auto-loading files?

In Microsoft Teams, only users with the required Teams permissions can modify tab settings. Typically, team owners and some IT administrators can change tab configuration. Regular team members usually have limited control.

Why do I have to keep uploading my files whenever the tab is opened?

  • If file links are configured in the Teams tab settings, those files load automatically when the tab opens. You can remove or replace them later.
  • If file links are not configured, users must open files manually each time.

Why does the IFC Viewer reload every time I switch tabs?

This is standard browser behavior in Microsoft Teams. Two workarounds:

  1. Pop out the tab - click the pop-out icon to open the viewer in a separate window. The model stays loaded as long as the window is open.
  2. Save a BCF view - save your current view as a BCF file and store it in SharePoint. Configure it as the default view in the tab settings. The viewer will reload that view automatically each time the tab is opened.

Does everyone see whenever I open a file or which part I am viewing at?

No. Other users in Teams do not get a notification when you open a file in IFC Viewer. Each user has an individual view. The model view does not synchronize between users unless you use screen sharing or another collaboration method.

Data and processing

Does the IFC Viewer for Microsoft Teams send any telemetry or IFC data to Flinker?

No. The IFC Viewer for Microsoft Teams does not send any IFC or BCF content to Flinker. Only minimal technical metadata is processed, as described in the architecture and data protection documentation.

Is IFC parsing performed entirely in the browser?

Yes. The IFC Viewer for Microsoft Teams parses and processes IFC files entirely client-side in the browser. No IFC model data is sent to Flinker services. For more details, see the architecture and data protection documentation.

Filters

Are there built-in standard filter presets in the viewer?

No. The IFC Viewer does not ship with pre-defined filter presets. Filters are created by the user based on the properties available in the loaded IFC model.

The recommended approach is to create your own standard filters once and save them as a BCF file. Because filter state is stored inside the BCF file as part of the open BCF standard, you can load that file in any Teams channel or project to restore the full filter configuration instantly - without manual recreation. Store the BCF file in a shared SharePoint location to make it available across all projects that use the same filter setup.

Last updated on 2026-03-26
Raise issue