Skip to main content

Understanding the GCXONE Hierarchy Model

The GCXONE platform uses a 5-level hierarchical structure to organize security assets, manage access control, and ensure data isolation. Understanding this hierarchy is essential for effective platform administration and configuration.

🏗️

5 Levels

Complete Organization

Core Benefits​

🔒

Data Isolation

Complete separation between tenants and customers

🎯

Access Control

Granular permission management at every level

📈

Scalability

Easy organization for organizations of any size

📍

Asset Tracking

Accurate tracking of devices and alarms

GCXONE Hierarchy Diagram

The 5-Level Hierarchy Structure​

Level 1: Tenant

Top-level organization with completely isolated data and configuration

Key Characteristics

  • Complete Data Isolation: Each tenant operates in its own dedicated space
  • Independent Configuration: Custom settings, branding, and integrations
  • Subdomain Access: Unique subdomain (e.g., company.nxgen.cloud)
  • Multi-Customer Support: Can serve multiple customers (MSSP model)

Common Use Cases

  • Managed Security Service Providers (MSSPs)
  • Large enterprises with multiple divisions
  • Service providers offering white-label solutions

Example Structure

Tenant: "Security Solutions Inc."
├─ Customer: "Retail Chain A"
├─ Customer: "Manufacturing Corp B"
└─ Customer: "Healthcare Group C"

Hierarchy Benefits​

🔒

Data Isolation

Complete separation at every level ensures customer data never spills over between tenants, customers, or sites.

🎯

Access Control

Granular permissions enable precise access management. Users can be granted access to specific customers, sites, or devices.

📈

Scalability

Supports organizations of any size, from small businesses with few sites to enterprises with hundreds of locations.

Common Hierarchy Patterns​

Single Organization

Tenant: "My Company"
└─ Customer: "My Company"
  └─ Site: "Headquarters"
      └─ Device: "Main NVR"

Multi-Location Business

Tenant: "Retail Corp"
└─ Customer: "Retail Corp"
  ├─ Site: "Store 1"
  ├─ Site: "Store 2"
  └─ Site: "Store 3"

MSSP Model

Tenant: "Security Provider"
├─ Customer: "Client A"
│   ├─ Site: "Office"
│   └─ Site: "Warehouse"
└─ Customer: "Client B"
  ├─ Site: "Retail Store"
  └─ Site: "Distribution"

Integration with Talos CMS​

🔗 Seamless Integration

Automatic Synchronization

  • ✅ Sites created in GCXONE automatically appear in Talos
  • ✅ Alarms attributed to correct site and device
  • ✅ Bidirectional updates maintain consistency
  • ✅ Events correlated based on hierarchy relationships

Technical Implementation

  • MQTT Messaging: Real-time synchronization
  • Dedicated Proxies: Handle message routing
  • Error Handling: Retry logic maintains reliability
  • Event Correlation: Hierarchy-based event matching

For more information, see GCXONE & Talos Integration.

Best Practices​

✅ Do's

  • Use clear, consistent naming conventions
  • Ensure site addresses are accurate for Talos sync
  • Always assign unique Server Unit IDs
  • Organize sites and devices logically
  • Document tenant-specific configurations

❌ Don'ts

  • Don't reuse Server Unit IDs across devices
  • Don't use vague or ambiguous names
  • Don't skip address validation for sites
  • Don't mix different customer data
  • Don't ignore hierarchy when setting permissions

Need Help?​

If you need assistance understanding or configuring the hierarchy model, check our Troubleshooting Guide or contact support.