Tenant-resident files
Project files remain in SharePoint or the Microsoft storage location your organization governs.
SECURITY AND ARCHITECTURE
Data control by architecture, not by contract.
Flinker works inside the Microsoft environment your organization already secures, operates, and audits.
Read the technical documentation Your Microsoft tenant
Microsoft Entra ID Identity and access
SharePoint Files and permissions
Your browserLocal IFC model processing
Works across Microsoft 
Microsoft Copilot 
Microsoft SharePoint 
Microsoft Teams 
Microsoft Power BI Microsoft Azure
Microsoft Copilot Microsoft SharePoint Microsoft Teams Microsoft Power BI Microsoft Azure CORE PRINCIPLES
Designed to fit an enterprise Microsoft control plane.
Browser-side processing
Supported viewer workflows parse and render model data in the browser rather than staging it on a Flinker file platform.
Microsoft identity
Access follows the Entra ID, Microsoft permissions, MFA, and guest policies already in place.
Governed deployment
IT administrators retain control over app approval, rollout, access, and update procedures.
DATA FLOW
Know where every part of the workflow runs.
Architecture differs by product and deployment option. The technical review should confirm the file source, processing boundary, identity path, and any optional service before approval.
| Layer | Typical boundary | Control to verify |
|---|---|---|
| Project files | Device, SharePoint, Teams, or another customer-selected source | Microsoft permissions, sharing policy, retention, and file ownership |
| Model processing | Browser memory for supported viewer workflows | Product version, browser policy, local cache, and export behavior |
| Identity | Microsoft Entra ID when the host requires authentication | User assignment, MFA, conditional access, guests, and consent |
| Application deployment | Microsoft app catalog, AppSource, Power BI, or approved web delivery | Administrator approval, allowed apps, version rollout, and update process |
| Optional enterprise services | Customer-hosted Azure or agreed service architecture | Region, logging, secrets, network boundary, support access, and deletion |
SHARED RESPONSIBILITY
Security remains an operating responsibility.
Customer organization
- Microsoft tenant configuration
- Identity, MFA, conditional access, and guest policy
- SharePoint and Teams permissions
- User assignment and application approval
- Retention, sharing, and project governance
Flinker product
- Documented application architecture
- Browser-side processing where supported
- Controlled product build and release practices
- Product security guidance and remediation
- Support under the applicable agreement
Microsoft platform
- Microsoft and Azure service controls
- Platform identity and access services
- Tenant audit and compliance capabilities
- Service availability and regional options
- Platform certifications and trust documentation
DEPLOYMENT READINESS
A clear path through technical review.
Use Flinker’s documentation to identify the administrators, approvals, permissions, and rollout steps needed for your target Microsoft surface.
- 01 Review architecture Confirm data boundaries, browser processing, metadata handling, and service dependencies.
- 02 Map responsibilities Identify SharePoint, Teams, Power BI, Entra ID, and application administrators.
- 03 Approve the application Follow the documented Microsoft admin and consent path for the selected solution.
- 04 Pilot and scale Validate with a controlled project, then extend through standard enterprise deployment practices.
SECURITY REVIEW
Common questions, documented.
Where are project files stored? +−
Files remain in the Microsoft environment configured for the workflow, such as SharePoint.
Does Flinker require a separate model repository? +−
The solution is designed to work with project files in the Microsoft tenant rather than requiring a second repository.
How is access controlled? +−
Access follows the applicable Microsoft and Entra ID permissions, roles, and organizational policies.
Where can IT review the technical detail? +−
The documentation includes architecture, data protection, deployment, and product-specific administration guidance.
REVIEW PACKAGE
Give administrators the source material they need.
Architecture and data protection
Data boundaries, processing, privacy, and product architecture.
Open resourceIT administrator quickstart
Roles, approval preparation, deployment, and rollout responsibilities.
Open resourceAdmin-approved installation
Application approval and installation path for Microsoft.
Open resourceData processing documents
Current DPA, technical measures, and controlled service documents.
Open resourceBring your security team into the conversation early.
We’ll walk through architecture, Microsoft responsibilities, and the deployment path for your environment.