Multi-Location & Franchise Accounts¶

If your organisation operates more than one facility — or if you manage access control on behalf of multiple clients — DragonFly Cloud Portal supports a hierarchical account structure that keeps each location's data separate while giving you visibility across all of them from a single login.

How It Works¶

DragonFly Cloud Portal uses a tenant hierarchy to organise accounts. Every user, instance, and piece of data belongs to a tenant. When you log in, you see data for your tenant and everything below it in the tree — but nothing belonging to other branches.

DragonFly (root)
└── Your Franchise Group
    ├── Location A
    │   ├── Front Door
    │   └── Gym Floor Door
    └── Location B
        └── Front Door

A user at the Franchise Group level sees all locations and all doors. A user at Location A sees only Location A's doors. A user assigned to a single door sees only that door.

Tenant Types¶

Type	Typical use
Franchise Group	A group of franchises or regions under one organisation
Franchise	A single franchise location group
Facility	An individual gym, studio, or site
Door	A single access point within a facility

Your account type was configured when DragonFly set up your organisation. Contact [email protected] if you need to add a new location or restructure your hierarchy.

Viewing All Locations¶

Multi-location overview is managed by DragonFly. Contact [email protected] for a consolidated view of all your locations or a status summary across sites.

Per-Location Access¶

To give a location manager access to only their own site:

Create a user account for them with your admin login
Set their tenant to the specific Facility or Door they manage
Assign the appropriate role (Manager or Operator for day-to-day ops)

That user will only see their own instances when they log in — they cannot see other locations.

See User Roles for role options.

Shared vs. Isolated Data¶

Data type	Scoped to
Access logs	The instance (door) that generated them
Member/barcode database	The instance — each door has its own local cache
Schedules	The instance
Users	The tenant they are assigned to (and subtree access)
Reports	Visible to your tenant level and above

Members do not automatically share across locations. If a member needs access at multiple sites, their barcode must be present in each site's gym software or CSV.

Adding a New Location¶

New locations are provisioned by DragonFly. To add a site:

Purchase and install the hardware — see Hardware Setup
Email [email protected] with the new site name and which account it belongs to
DragonFly will create the tenant entry and link the new instance to your hierarchy

Once added, DragonFly will confirm when your new site is live.

Reporting Across Locations¶

Users with Manager-level or above access at the Franchise Group or Franchise level can view reports that aggregate data across all locations in their subtree.

For aggregated reports across all sites, use Dashboard → Statistics on each individual device, or contact support for a consolidated report.

For Franchise Owners & Admins¶

If you own or administer an organization, the Cloud Portal gives you the full picture in one place: your org tree, every door you're responsible for, schedules, denied barcodes, your team's accounts, and reporting.

Managing Your Organization Tree¶

The Organizations page shows your organization and everything beneath it as an expandable tree. Each node shows its name, type, and how many doors sit under it. From here you can add a child organization, rename or move a node to a different parent, or deactivate an organization — deactivation is a safe "soft delete" that first shows an impact summary of the affected users and instances before you confirm.

The Instances Page¶

Instances lists every door controller you manage — its name, online/offline status, relay and failsafe state, uptime, last check-in time, and which organization it belongs to. Click View on any row to open that instance's full detail page.

Multi-Door Sites¶

Some locations run more than one controlled door (front entrance, side door, a locker-room gate) from a single controller. On the Instances page these show a small arrow/chevron next to the name — click Show doors to expand the individual doors nested underneath, each with its own status and its own door page. Inside an instance, a strip of pills lets you switch between Global (Instance View) and each individual door; each door has its own lock state, schedule, and access log.

For a walkthrough of the portal home, instance cards, and instance detail, see the Client Portal Guide.

For Billing Partners¶

If you support clubs on behalf of a membership platform (Zenoti, Antaris, Paramount Acceptance, ABC Financial, Glofox, Fliip, and similar), your portal account sits one level below DragonFly in the tree. You see and manage everything under your own branch — your clients' franchises, facilities, and doors — but not other partners' clients or DragonFly's internal portal settings.

Onboarding a New Client Instance¶

When a brand-new DFACS box is plugged in at a client site, it phones home and lands in a holding area called the Onboarding Queue before it's usable:

Registration — the unit connects for the first time and reports its device ID, software version, and integration type. The portal creates a record automatically and shows it in the queue as "Not yet provisioned."
Onboarding queue — you see it listed with friendly name, device ID, version, integration type, and how long it's been waiting.
Assignment — click Onboard to open the wizard: confirm the device details and give it a real friendly name, assign it to an existing client facility (or create one inline), then confirm. The instance moves out of the queue, attaches to that facility, and receives its configuration.

Once assigned, the box switches from its provisioning splash screen to normal operation and appears on your Instances list like any other managed door.

Monitoring Client Health¶

Three places give you the health picture across your clients:

Dashboard — aggregate online/offline counts and 24-hour access volume across every client instance you can see, plus a recent-activity feed.
Instances list — per-instance status, uptime, and last check-in time, with a counter that flags anything offline more than 30 minutes.
Reports — an Instance Health view and a per-client Tenant Summary, useful for a quick sweep across many clients at once.

Remember that an instance flagged Offline in the portal has not necessarily stopped controlling access — DFACS keeps working locally without a network connection. Offline means the portal has lost contact with it. See the FAQ.

Configuring & Supporting Clients¶

Each instance's Configuration tab is a live, editable mirror of the door controller's own on-site configuration screen, where the integration type and its credentials (API keys, subdomain/location identifiers, sync timing) are set. Edit the values and save, and the change is pushed to the door over the cloud connection — so you can set up and troubleshoot a client's connection to your platform remotely, without a site visit. See Client Portal Guide → Configuration for who can edit versus view configuration.

When diagnosing a client's "member was denied who shouldn't have been" report, the fastest path is the instance's Access Logs tab: the Reason column names exactly why the door made its decision, which almost always traces back to that member's current status on your platform rather than a door-side problem.

See User Roles for exactly what each role can and can't do.