BOX 3.x

Operator workplace

Review sources and events using the permissions and modules in your BOX delivery.

Browsing: BOX 3.0 / 3.2

Begin with visibility

Confirm the correct site, camera and time range and the role’s allowed scope. Video walls and event journals serve different purposes: stream playback is not proof that events are being stored.

BOX 3.2 training operator: the camera-access summary shows one camera granted by the role and no additional cameras
BOX 3.2 training operator: the camera-access summary shows one camera granted by the role and no additional cameras. Check actual visibility by signing in as the operator. Localized reference view; captured settings and values are preserved.

Review an event

Open the event card, inspect the available evidence and context, and compare the observed situation with the scenario’s event definition. Check camera/time identifiers and note missing or ambiguous evidence.

BOX 3.2: compare the detected fragment with the original frame, then review the decision, required field and comments
BOX 3.2: compare the detected fragment with the original frame, then review the decision, required field and comments. Shown with administrator access; the available controls depend on the assigned role. Localized reference view; captured settings and values are preserved.

Record a decision

Use the configured verification actions and comments. Apply bulk changes only to the intended selection after reviewing filters and scope. The exact statuses and export options depend on the release.

Escalate recurring issues

Record the source, interval, example event and expected behaviour. Route stream/media faults to operations and scenario-quality issues to the analytical team. Do not attempt to solve access or infrastructure faults by changing event labels.

Verify the saved decision and history

After submitting a decision, reopen the record and check the saved status, comment and history, including who changed it and when. A decision confirming a violation and a record of measures taken are separate actions. When evidence is missing or ambiguous, follow the configured additional-review process rather than assuming confirmation.

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