Skip to main content

User Guide

Welcome to the ION Guard documentation — the security monitoring and operational management platform by ION Grade.

What is ION Guard?​

ION Guard is a modular security monitoring platform designed to centralize the operation of multiple sites and technologies in a single interface. It provides the foundation — multi-tenant management, profile-based access control, alert engine, reports, audit, and real-time communication — on top of which specialized modules add specific capabilities based on each operation's needs.

The platform works independently. Modules are optional and enabled per site, allowing each location to have exactly the features it needs.

What the platform offers on its own​

  • Command Center — Interactive map with a consolidated view of all sites and real-time alerts
  • Alert engine — Receives, displays, escalates, and logs alerts from any module, with full lifecycle (active → acknowledged → resolved)
  • Multi-tenant management — Multiple isolated organizations, each with their own sites, users, and settings
  • Access control — 5 hierarchical profiles (Platform Admin, Tenant Master, Tenant Admin, Operator, Viewer) with granular permissions
  • Sites, floors, and zones — Organizational structure to represent physical locations with floor plans and monitored areas
  • Reports — Asynchronous generation with export in CSV, XLSX, and PDF
  • Audit — Immutable record of all changes with before/after comparison
  • Real-time communication — WebSocket for instant alert and event updates
  • REST API — Full interface for integration with external systems

What modules add​

Modules extend the platform with specialized capabilities:

ModuleWhat it adds
SynapsysBLE tracking of people and assets, panic alerts, zone-based location, security analytics
DigiEyeTriggering physical outputs (sirens, relays) in response to alerts, via MQTT gateways
AcceleroMonitoring of Accelero access control systems, with status dashboard and MQTT integration

Each module brings its own devices, alerts, reports, and pages — but all integrate with the platform's Command Center, alert engine, and audit.

Who is this guide for?​

ProfileWhat you do on the platform
OperatorMonitors the Command Center, responds to alerts, tracks the operational status of assigned sites
ViewerViews dashboards, alerts, and reports without performing actions (read-only)
Tenant AdminManages sites, zones, operational users, and day-to-day settings
Tenant MasterFull access to the organization — settings, all sites, all users
Platform AdminAdministers the platform as a whole — organizations, modules, certificates, system settings

Core concepts​

Organizational hierarchy​

Organization (Tenant)
└── Site (physical location)
    ├── Floor (level with floor plan)
    │   └── Zone (monitored area)
    └── Enabled modules (per site)
  • Organization (Tenant) — A company or client entity. Each organization has its own isolated sites, users, and data.
  • Site — A physical location: building, factory, hospital, distribution center. Everything on the platform is organized by site.
  • Floor — A level within the site, with an optional floor plan for map visualization.
  • Zone — An area within a floor: room, corridor, courtyard. Zones have types (Restricted, Common, External) that can influence module behavior.

Alerts​

Alerts are the central mechanism for communicating events on the platform. Any module can generate alerts, and the platform manages their lifecycle:

Active → Acknowledged → Resolved
          ↗
   Escalated (automatic, if not handled within the deadline)

The alert types available depend on the modules enabled at each site.

Modules​

The platform is modular by design. Modules are installed by the Platform Admin and enabled per site — one site can have Synapsys + DigiEye, another can have only Accelero, and a third can operate with just the base platform.

See Modules for details on enabling and managing modules.

Next steps​