ViewLogicTechnical CenterViewLogic website
Documentation / BOX 3.x
BOX 3.x

BOX 3.x administrator workflow

Configure access, sites, sources, rules and operating checks in a controlled order.

Updated 27 September 2026
Browsing: BOX 3.0 / 3.2

1. Access and roles

Check the environment address, trusted certificate, authentication and required network access. Use a supported browser. Separate administrative and review responsibilities and verify permissions with a test account.

Shared access module, illustrated in BOX 3.2: role name, priority, camera scope and permission tree
Shared access module, illustrated in BOX 3.2: role name, priority, camera scope and permission tree. This new-role form has no completed operator permissions.

2. Sites and cameras

Create the enterprise/site hierarchy before adding cameras. Record stream or VMS access, site assignment, responsible users, zones, schedules and analytics settings. Verify playback, archive where required, time synchronisation and actual frame rate before bulk assignment.

BOX 3.2: the new-site form, with name, parent path, map and image fields
BOX 3.2: the new-site form, with name, parent path, map and image fields. This blank form explains the inputs; it does not show a saved Sigma site.

3. Scenarios, zones and decision rules

Use validated analytical configurations. Match zones to the actual camera view and re-test after any camera movement or optical change. The decision matrix classifies and routes outcomes. Trace one camera through detection, event creation, evidence, review and notification before expanding.

Shared decision module, illustrated in BOX 3.2: combine camera, primary category, rule type and zone conditions, then choose a decision
Shared decision module, illustrated in BOX 3.2: combine camera, primary category, rule type and zone conditions, then choose a decision. The displayed Ignore choice is an example, not the required rule for every case.

4. Users and reference data

Configure roles, employees, sites, event types, zones, presets and the reference data included in the delivery. Test directory-group mapping and identity-provider interruption where used. Validate bulk imports in an isolated environment.

Shared access module, illustrated in BOX 3.2: the account wizard links login details, roles and interface language
Shared access module, illustrated in BOX 3.2: the account wizard links login details, roles and interface language. The example values are for training; the administrator supplies real credentials.

5. Operations

Monitor cameras and services, input/processed frame rate, CPU/GPU/memory, queues, errors, storage and event delivery. Include audits, backups, restore tests, licensing, cleanup and notification checks in the operating procedure.

Server Monitoring, illustrated in BOX 3.2: service groups and Grafana metrics help investigate resource usage and errors
Server Monitoring, illustrated in BOX 3.2: service groups and Grafana metrics help investigate resource usage and errors. This view does not demonstrate a Loki query or an Explore session. Localized reference view; captured settings and values are preserved.

6. Handover

Run a control scenario for each role and verify visibility, event actions and exports. Hand over a service map, escalation contacts, backup policy and version history.

Configuration locations

LocationPurpose
domain.conf / domains.confEnabled domains; exact filename depends on release
Inference domain .envProcessing and video-transport parameters
ui-rest/ui-config/settings.jsonFeature settings in applicable builds
ui-rest/ui-config/config.jsonFrontend settings such as DEFAULT_LANGUAGE
.env and service environmentBackend settings such as USER_DEFAULT_UI_LANG

Field-level instructions for the administration workflow

Use the shared chapters for application settings and the BOX 3.2 chapter for the exact camera form. Presets, zone settings and the decision matrix are separate configuration layers; verify each before handing the camera to an operator.

Use the documentation and configuration supplied for your installed release. Environment addresses and access credentials are provided privately with the delivery.