Public tenant preview
Four tenants. One project truth. Different workspaces for the work each team owns.
This fictional example shows how an end user, integrator, consultant, and manufacturer can work from the
same physical security project while keeping internal notes, approvals, files, and action ownership in the
right tenant view.
Overview
Action Center
Questions / Approvals
Budget
Executive Summary
Files
SOW
BOM
Change Requests
Project Chat
Open actions4
Budget confidence67%
Vendors attached3
Next stepUpload evidence
Upload door scheduleBlocks SOW and BOM confidence.
Confirm identity providerNeeded before integration scope can be finalized.
Approve clarification packageReady for vendor response.
Intake Review
Files
AI Analysis
Clarifications
Labor Risk
Submit to Manufacturer
Files reviewed8
Open clarifications5
Labor riskMedium
RouteManufacturer scope
Run installation readiness reviewIdentify cabling, access, and site readiness gaps.
Resolve controller reuse questionAffects labor estimate and migration plan.
Prepare manufacturer-dependent scopePackage assumptions for technical review.
Design Center
RFI Center
Addenda
Spec Matrix
Submittals
Closeout
Open RFIs6
Pending addenda2
Spec exceptions4
Owner approvals3
Reconcile drawings and schedulesFlag device count conflicts before bid response.
Draft addendum languageConvert approved clarifications into bidder-safe output.
Mark owner approval requiredSubstitution request needs decision before publish.
Technical Review
Product Assumptions
Compatibility
PS Scope
SOW
BOM
Assumptions9
Compatibility flags3
PS dependencies4
DecisionReview needed
Validate target architectureConfirm whether cloud, on-prem, or hybrid assumptions apply.
Flag unsupported assumptionsPrevent scope language from becoming a hidden promise.
Return review packetSend first-pass technical notes back into the project workspace.
