Skip to content
Duall Master

Use case

Run every site from one console — without flattening local control

Portfolios grow site by site, and so do the tools. Duall Master gives you one identity model, one policy framework, and one operating picture across every location — while each site keeps the local permissions and structure it needs.

One command surface

Module-by-module rollout

Audit-friendly operations

Multi-site centralized control operating context
Multi-site centralized control command view
Duall Master product interface for Multi-site centralized control

How it plays out

The scenario, step by step on one timeline.

Each step ties to a real platform action — not a slideshow.

Live site signals
Shared operating context
Governed response
Reviewable history

Journey step 01

Foundation

Identity, roles, and policy are defined once at the portfolio level.

Before and after

Before Duall Master

Each site on its own system, with its own logins and exports

No portfolio-wide view of access, visitors, or incidents

Policy changes repeated by hand at every location

Onboarding a new site means standing everything up again

After Duall Master

Shared identity, policy, and site structure

Live events with module context attached

Governed operator actions with audit history

Phased expansion without replatforming

Most relevant modules

Module combinations for this use case

This use case starts with the module that solves the clearest operational pain, then expands on the same foundation.

Module stack

One operating picture, assembled module by module.

Shared foundation

Identity & policyRealtime eventsAudit historyAPIs & deployment
Duall Master module stack for Multi-site centralized control

Live operations layer

Access, visitors, parking, video, intercom, and audit events resolve into the same command surface.

Scenario operating model

Multi-site centralized control needs connected site signals, not another point solution.

Tap any layer to see how it helps a buyer evaluate the platform.

Step 01

Signal

Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.

01Signal

Doors, visitors, cameras, intercoms, parking, and devices generate live operational signals instead of isolated alerts.

02Context

Each signal becomes useful because operator, person, role, site, zone, policy, and related module records are shown together.

03Action

Teams approve, deny, review, escalate, annotate, or link evidence without leaving the command surface.

04Audit

Every decision keeps the who, what, when, why, and related evidence needed for handoff, reporting, and investigation.

Buyer-facing model for phased adoption: start with the clearest pain, then add adjacent modules on the same foundation.

Deployment and trust

Shared identity and tenant-aware permissions across sites
Central policy with per-site overrides
One cross-site operating picture and audit trail

Typical adoption path

  1. 01Establish shared identity and policy at the portfolio level
  2. 02Bring sites onto the same foundation one at a time
  3. 03Operate, report, and audit across the whole portfolio

Next step

Discuss Duall Master for Multi-site centralized control

Review module priorities, deployment constraints, integrations, and rollout path for your environment.