About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
Direct answer: Represent franchise and corporate groups as an explicit organisation hierarchy—holding company, legal entities, sites, brands—with data isolation rules, consolidated reporting paths and billing ownership documented per node, instead of pretending one “tenant” equals one ABN or one database schema fits every franchise contract.
Why it matters
Franchisors want roll-up dashboards; franchisees want their data walled off from competitors sharing your platform. Corporate groups acquire subsidiaries that must stay legally separate but share chart of accounts templates. A naive one-tenant-one-database model forces painful workarounds: duplicate logins, hidden cross-queries, or dangerous shared tables.
This is the commercial entity model for ISVs, not the infrastructure choice between dedicated hosts and shared pooled resources (see what private cloud means on shared hardware for deployment-model vocabulary). Hosting still matters: network segmentation and backup scope follow the hierarchy you sell.
How it works
Concepts to name in your product
- Organisation node — company, trust, or franchisee unit with its own tax identifiers.
- Site or location — physical or logical branch under a node.
- Brand — white-label surface that may span nodes.
- User membership — which nodes a principal can act within (scoped roles).
Isolation patterns
| Pattern | Isolation | Roll-up |
|---|---|---|
| Separate tenant per franchisee | Strong | Harder; needs aggregator |
| Shared app, row-level org key | Flexible | Easier; needs rigorous engineering |
| Hybrid | Franchisee tenants + franchisor read models | ETL or replicated summaries |
Logical separation on shared platforms needs automated tests that franchisee A never reads franchisee B even when queries are crafted maliciously—partner impersonation and support tools included. The ASD Information Security Manual notes that an actor who compromises one operating environment might exploit a flaw in an underlying software-based isolation mechanism and thereby compromise other operating environments—treat cross-node access as a security test problem, not an assumption.
Billing
Decide: bill franchisor centrally with usage allocation, or bill each franchisee. Subscription metadata should attach to the contracting node, not only the top brand.
Workflow
Approvals may route up the hierarchy (capital spend) or down (policy push). Time zones and public holidays differ per site—link to per-tenant calendar configuration.
On paper exercise
Draw one real customer: franchisor, two franchisees, one corporate store, overseas trial. Mark which reports cross nodes, which integrations are per-site VPN, and which support tickets the franchisor can see.
What to choose and why
Retail franchises often need strong isolation and simple roll-up via nightly aggregates. Professional services groups may accept multi-entity in one tenant with strict role separation if regulators allow.
Sell hierarchy as a SKU—implementation services explode when you discover franchise nuances after quoting “standard tenant.”
Read next
Related articles you may want next.
- HostingWhat partners need to see that end customers should notGive partners the oversight they need while protecting each customer’s data through tenant boundaries, limited permissions and clear support access rules.Read article
- HostingTime zones and financial calendars when Australian customers share a hosted stackDesign time zones, daylight saving and financial calendars for Australian customers so scheduled work and reports use the intended business dates.Read article
- HostingWhat "private cloud" means: shared hardware, dedicated hosts and the questions to askHow the standard definition of private cloud differs from the way the term is used in hosting offers, what shared tenancy, dedicated instances and dedicated hosts each isolate, and the questions that establish what an offer actually provides.Read article
Risks and limits
- Reorganisations (buyouts) require merge and split tools; ad-hoc SQL merges are audit nightmares.
- Cross-node search features are leakage hotspots.
- Export and portability must respect node boundaries for exit packs.
- Not legal advice on franchising law or related-party trading.
- Hierarchy features not lab-tested in this article.
Sources
- Multi Tenant Security Cheat Sheet — OWASP; accessed 2026-11-16 — tenant isolation and authorisation design patterns.
- Guidelines for system hardening — ASD ISM — ISM September 2026 edition; accessed 2026-11-16 — software-based isolation failure modes across operating environments.
- The NIST Definition of Cloud Computing, SP 800-145 — September 2011; accessed 2026-11-16 — multi-tenant resource pooling (not isolation guidance).
Related reading
- What partners need to see that end customers should not
- Time zones and financial calendars when Australian customers share a hosted stack
- Choosing pilot users inside the customer's organisation before full go-live
- What private cloud means on shared hardware (deployment vocabulary)
- Software vendor hosting (related service context)
Learning notes
- Franchises need an explicit org graph, not extra user accounts.
- Roll-up reporting and isolation trade off—choose deliberately.
- Billing node and data node may differ—document both.
- Test cross-node access like security features, not afterthoughts.
- Model one real hierarchy on paper before signing enterprise deals.
This article was originally published on .