Multi-hub governance
for every network topology.
Sympl · CMMS is built for organizations with multiple entities — corporate HQs with plant hubs, MSPs with client portfolios, franchisors with franchisees. One network portal to govern all of them, with rollup analytics, catalog inheritance, policy enforcement, and granular identity controls.
Network topologies
Built for organizations with multiple entities under one account.
The network model is the same regardless of the relationship. A parent entity governs child hubs — with a consistent portal, policy engine, and rollup layer across all four topologies.
Corporate HQ → Business units
A corporate FM or VP Maintenance governs 8–50 plant hubs under one account. Push approved vendor lists, mandate critical-asset PM frequencies, and see compliance posture at a glance across every site.
MSP → Client hubs
An MSP operator manages 20–200 client hubs. Push standard templates to all clients, surface alerts across the entire portfolio, track SLA compliance, and deploy catalog updates to every client at once.
Franchisor → Franchisees
Ensure franchisees use approved vendors, follow mandatory PM schedules, and maintain brand and warranty compliance — without building a custom portal.
Regional manager → Site cluster
An exception-based view across 3–15 sites: what's overdue, what's at risk, where a region stands relative to peers. Governance without replacing each site's operational workflow.
Network portal
Governance without operations.
The network portal is not an operational tool — no work orders to assign, no assets to wrench on. It exists to push standards down, see aggregated health across child hubs, and track compliance without replacing each site's day-to-day workflow.
Rollup dashboard
Cross-hub KPIs in one view — open work orders, overdue criticals, PM compliance %, and asset health score per child hub. Exception-first layout surfaces problems, not just summaries.
Compliance scorecards
Per-child hub compliance scorecard for every active policy. Per-policy drill-down shows which assets or entities are the gap — and the trend over time.
Catalog manager
Manage the master catalog — vendors, parts, equipment classes, PM templates, failure modes — and see per-child inheritance status. Which children have adopted, which have overridden, which fields are locked.
Policy library
Author and enforce network-wide standards: PM mandate frequencies, approved/blocked vendor lists, safety checklists on qualifying asset classes, data quality thresholds. Tracked or fully enforced.
Catalog inheritance
Push master data down. Let child hubs know what's locked.
The parent hub maintains a master catalog — vendors, equipment classes, failure modes, criticality models, PM templates. Changes propagate to all child hubs via the sync engine.
Every catalog row shows its inheritance status. Child hubs can see which fields are locked by the network and which they're free to extend locally. Locked fields are read-only with a "Set by your network" badge — there's no silent enforcement.
Vendors, equipment classes, and failure modes pushed to all children
PM templates inherited and customizable within parent-set bounds
Per-field locking — lock critical fields, leave others flexible
Override visibility — parent sees which children have deviated
Master catalog row — child hub view
Policy library
Four policy types. Three enforcement levels.
Author network-wide standards in the policy library and track compliance across every child hub — from informational guidelines through full enforcement.
PM Mandate
"All centrifugal pumps must have an active PM scheduled at ≤ 90-day intervals."
Evaluated nightly against each child hub. Child admins are notified of gaps. Parent sees per-child compliance score.
Vendor Policy
"ACME Bearings is approved account-wide. Fly-by-Night Supply is blocked."
Propagated via the catalog sync engine. Child hub vendor records carry approved/blocked status automatically.
Safety Requirement
"Any work order on a medium-voltage asset must include a lockout/tagout checklist."
Evaluated against WOs on qualifying asset classes. Gaps surface as compliance failures on the scorecard.
Data Quality
"All assets must have make, model, and serial number populated (≥ 95% compliance)."
Threshold-based compliance check run nightly. Helps enforce data standards across every child hub.
Enforcement spectrum
Parent publishes a standard. Child can see it in their "Network standards" view, but nothing is measured or enforced. Useful for publishing guidelines before enforcement is ready.
Compliance is measured nightly. Parent sees per-child scores. Child admins are notified of gaps. No UI lockout in the child hub. The right default for most policies.
Child cannot deviate. Locked fields are read-only with a "Set by your network" badge. Mandatory PM templates cannot be deleted. Blocked vendors cannot be unblocked.
Identity & access
Enterprise-grade identity, built into the data plane.
SSO, granular RBAC, member type ceilings, service accounts, and append-only audit logging — available in every hub, not bolted on as a separate add-on.
SSO / SAML via WorkOS
Connect your identity provider — Microsoft Entra, Okta, Google Workspace, or any SAML 2.0 / OIDC provider. User provisioning and deprovisioning sync automatically.
Granular RBAC with site-level scopes
Role grants can be scoped to specific sites, asset classes, or criticality levels. A contractor can be granted technician access to one site only — without any hub-wide visibility.
Member type ceilings
Every principal has a member type — internal, contractor, vendor, customer, auditor. Member type sets a hard permission ceiling that no role grant can exceed, even by misconfiguration.
Service accounts & API tokens
First-class service account principals with declared permissions and scope. API tokens inherit the service account's effective permissions intersected with the token's declared set — no over-privileged integrations.
Append-only audit log
Every invite, grant, revocation, member-type change, suspension, token issuance, and assignee change is written to an append-only per-hub audit log. Queryable, exportable.
Multi-hub jump access
A network user can jump directly into any child hub's operational portal from the network dashboard — no separate login — with normal hub-scoped session auth.
Data isolation
Schema-per-hub isolation. No shared tables between hubs.
Every hub lives in its own PostgreSQL schema. There are no cross-hub queries at the data plane level — hub data cannot leak to another hub by misconfiguration. Rollup analytics use a delegated fan-out via the API layer, never direct cross-schema SQL.
International hubs hosted in their own zone.
Still rolling up to one dashboard.
For organizations operating across geographies, each regional or country hub can be hosted in its own cloud zone — EU, APAC, or any supported region. Hub data never leaves its designated zone, satisfying data residency requirements like GDPR without architectural compromise.
Local users connect to their nearest zone for lower latency. Meanwhile, the parent network portal aggregates KPIs, compliance status, and rollup analytics across all regions — without moving underlying data across borders.
EU West (Frankfurt)
EMEA operations
APAC (Singapore)
APAC operations
US East (Virginia)
North America HQ
Network rollup aggregates across all zones
without moving data cross-border
Data residency compliance
GDPR, PDPA, and other regional data sovereignty requirements are satisfied by keeping hub data in-zone — no legal workarounds needed.
Lower latency for local users
Technicians and site managers connect to their nearest zone. No cross-continental round-trips for work order operations.
Centralized governance, still
The parent network portal aggregates compliance scores, KPIs, and catalog status across all regions via the API-layer rollup — data stays put, insights cross borders.
Enterprise config
One platform. Any number of entities beneath it.
Whether you're managing 3 sites or 300 client hubs, the network portal, catalog engine, and policy layer scale with your organization.
it's that sympl.