Configuration

Configuration is the administrative hub for all site and device operations. It is the source of truth for your operational structure — which sites exist, how many cameras are connected, who the onsite contacts are, and each site’s current activation status. Every deployment and expansion workflow begins and is validated in Configuration. Covers: What Configuration Does, What Configuration Contains, Summary Cards.

What Configuration Does

What Configuration Contains

Summary Cards

The summary area at the top of Configuration shows different information depending on which tab is active. On the Added Sites & Devices tab, four cards group related real-time counts of your environment. Each card can be switched between a count and a percentage view, and collapsed. On the Spreadsheet Import tab, the same area shows import progress statistics instead: Total, Valid, Invalid, Failed, Created, Public Sites, Private/VPN Sites, Edge Deployment, and Active Sites. The four cards on the Added Sites & Devices tab are:

• SITES — site-level counts: Active and Inactive (by the 24-hour heartbeat rule — see Site Activity below), Devices (total cameras across all sites), and Online (cameras currently connected).
• DEVICES — camera-level counts: Active (onboarded and not Disabled), Inactive (added but not currently active), Online (currently connected to the platform), and Manual (configured by hand — see Manual Fallback in Adding Devices).
• DEPLOYMENT — a breakdown by connection mode: Public, Private, Edge, and Inactive (see Site Activity and Deployment Modes below).
• SITE STATUS — onboarding state across your sites: Done, Pending, Part. Pend., Error, and Part. Err. (each defined in Site Status States below).

Site Activity and Deployment Modes

Active vs Inactive. A site counts as Active when at least one of its cameras has sent a heartbeat or alarm within the last 24 hours. If every camera goes silent for longer than that, the site flips to Inactive. Recovering one is usually just camera-side connectivity: confirm the camera or NVR is online and reachable from outside the customer network (or that the Local Agent is still running for private sites), re-verify the credentials haven't been rotated, and if the camera replies but sends no alarms, check its SMTP/REST settings. The site returns to Active automatically on the next heartbeat or alarm — the site record never has to be re-created.

Deployment modes. Sites are also broken down by how cameras connect. Public IP is the fastest to onboard because the cloud auto-configures the camera with no field work — preferred wherever the camera is publicly reachable. Private/VPN is the most common for monitoring-station deployments where customers keep cameras off the public internet. Edge is for cameras that only stream video and cannot send alarms on their own. GC Edge software runs on a PC at the site, connects to the camera’s RTSP stream, and handles alarm detection locally. After setup, the GC Edge software must be armed manually before alarms flow — it does not arm automatically. The mix is whatever fits the underlying networks — there’s no price premium for one mode over another.

Sites Table

Under the Added Sites & Devices tab, the primary view is a table listing all registered sites. Each row shows: Site, Contact email, Device count, Connected devices, Disabled (indicates whether the site is currently disabled — Yes or No), Site key (the activation key distributed to the onsite contact), Status, and an Actions menu.

• Site Name — the unique identifier for this location. Appears in Video Search, Analytics, and subscription filters.
• Status — current site state: Active, or error states. See the Troubleshooting Guide for a full list of site status states and resolution steps.
• Device count — total number of cameras registered to this site.
• Contact email — email address of the onsite contact responsible for field activation.
• Connected devices — number of cameras currently sending events to the platform.
• Site key — the per-site activation secret, shown so you can view or rotate it. Rotating revokes the old key immediately and generates a new one — distribute it only to the rightful on-site contact. The Site Key never grants access to view cameras or alarms; it only authorises the one-time activation handshake between the Local Agent and the site record. Once a site is Active, rotating the key has no operational impact.
• Actions Menu (…) — per-site quick operations, accessed by clicking the three-dot button on any site row. Three actions are available: Add device — opens the device setup flow directly for that site without leaving the sites list; Forward alarms — opens the Forward Alarms dialog to configure CMS forwarding for that site (see CMS Forwarding); Send site key — resends the activation key to the onsite contact via WhatsApp or email.

Site Status States

The Status column shows where each site sits in onboarding. Resolution steps for problem states are in the Troubleshooting Guide; the states themselves are:

• Done — fully onboarded and operational. GC Surge marks a site Done only when four things succeed: every camera has a configured forwarding path, at least one heartbeat has been received from each camera, at least one test event has flowed through to Video Search, and the site has been Active for more than one full check interval. If any fail, the site stays in Pending, Part. Pend. or Error.
• Pending — created but not finished onboarding. Most Public IP sites move to Done within 5–10 minutes of credentials being entered; Private/VPN sites can stay Pending until the Local Agent runs on-site (expected). A Public IP site stuck in Pending for more than 30 minutes is worth checking — camera credentials, brand selection and the port number.
• Part. Pend. (Partially Pending) — the site is online but at least one camera hasn't finished onboarding while the rest are Done. Each camera carries its own state (Done, Pending, Error) in the site's Devices panel. The usual cause is credentials that differ from the rest of the site, or a misspelled brand on that one row.
• Error — at least one camera failed its configuration push. Open the Devices panel to see the last error per camera; the most common are connection refused (IP/port wrong or device offline), 401 Unauthorized (wrong camera username/password), and unsupported device profile (brand mismatch). Correcting the field is enough — the platform retries on the next health check, with no need to delete and re-add.
• Part. Err. (Partially Errored) — some cameras work while others have failed. Urgency depends on what's failing: tertiary cameras (overview shots, duplicate angles) can run in Part. Err. while you still get alarms from the working ones; cameras covering critical assets should be fixed promptly. Part. Err. sites count toward Inactive deployment density in Analytics, so a long-lived flag will skew reports.

Site Search

The search bar at the top of the table narrows the site list by name, filtering in real time as you type. Next to it, an All statuses dropdown filters the table by site status. Both are useful for accounts with many sites.

Camera Detail Panel

Clicking a site in the table opens a detail panel on the right side of the screen showing all cameras registered to that site. The panel has two tabs: All Cameras (all registered cameras for the site) and Failed (cameras with configuration or validation errors). A Send Site Key Via WhatsApp/Email button at the top right of the panel lets you resend the Site Key to the onsite contact without navigating away from the main table.

The Devices panel is also the recommended place to add a camera to an existing site: use + or Add a Device at the top and you skip straight to the device step without re-entering the site details. Reusing the site keeps the contact, deployment mode and Site Key consistent across every camera at that location.

Add Sites Controls

Configuration has two tabs: Added Sites & Devices (default view showing all registered sites) and Spreadsheet Import (bulk site creation via spreadsheet). To add sites or cameras, click ADD at the top right. Choose from four options: Guided Setup (recommended — walks you through the correct connection mode automatically), Add Sites Manually (fill in the form directly), Spreadsheet Import (bulk create via Excel template), or Connect a Single Device (REST API, SMTP, or FTP without Guided Setup). Contact info is optional if you are on-site yourself — tick I’m at this site — I’ll set it up myself instead.

Inviting Users

The Invite Admin button in Configuration is not yet active. All user invitations — including for administrator-level accounts — must be performed via the Users module. When enabled, Invite Admin will grant the Super Admin role — the most powerful on the platform, able to create and modify sites, manage users, and manage the subscription. Because every admin account is a potential attack surface, reserve it for people who genuinely need that control; for event-review-only staff, invite as Operator.

Standard Deployment Workflow

1. Create sites (manually or via spreadsheet import).
2. Validate that all site entries have correct contact details, names, and addresses.
3. Use the site Actions menu to distribute Site Keys to onsite contacts.
4. Monitor site status as field activation is completed — sites should transition to Active.
5. After activation, verify device counts match the expected camera count per site.
6. Identify and investigate any sites that remain in pending status beyond the expected activation window.

Data Quality & Governance

Configuration data quality directly affects downstream operations. Poor data here creates problems everywhere:

• Incorrect site names make it difficult to filter events in Video Search and produce confusing analytics reports.
• Wrong contact details mean Site Keys get sent to the wrong person, delaying activation.
• Missing device counts make it impossible to tell whether a site is fully activated or partially broken.

Assign one named owner responsible for Configuration data accuracy. This person should audit the site roster weekly during active deployment phases and monthly during steady-state operations.