MyProtektor

Operations Board for Incident Tracking

Board Layout

The Security Operations Board is a Kanban-style view that organises every incident in your system by its current stage. Open it from the sidebar under Incidents > Operations Board.

The board is divided into four columns, each representing a distinct phase in the incident lifecycle. Cards flow from left to right as incidents progress toward resolution.

Available to Admin and Owner roles when the incident reporting workflow is enabled for your organization.

Security Operations Board with four columns: Incoming, Dispatched, Attention, and Resolved showing incident cardsClick to expand

Tabs

The board has two tabs at the top:

  • Incidents shows all reported incidents.
  • Field Reports shows field reports submitted by guards.

Filters

At the top of the board, you have tools for narrowing your view:

  • Search bar. Find incidents by title, type, or severity.
  • Severity dropdown. Filter by All, Critical, High, Medium, or Low.
  • Time filter. Narrow to Last 24 Hours, Last 7 Days, Last 30 Days, or All Time.

These filters are useful during shift handovers when the incoming operator needs to focus on recent high-severity items without scrolling through the full history.

Three Views

You can switch between three views of the same data:

  • Board. The default Kanban layout with draggable cards in four columns.
  • List. A vertical list of all incidents, grouped by status.
  • Table. A spreadsheet-style view with sortable columns.
Board with search bar, severity filter, and time range dropdown open showing All Time through Last 30 Days optionsClick to expand

What Each Column Means

Incoming

New incidents that have just been reported and have not yet been picked up. This column contains:

  • Panic alerts triggered by guards or clients through the mobile app
  • New incident reports submitted from the field
  • Any report that has not yet been acknowledged or assigned

If cards are sitting in this column, they need someone to review and act on them. During a shift, this is the first column you check. An empty Incoming column means every report has been acknowledged.

Dispatched

Incidents where a guard has been assigned and is responding. A card moves here when:

  • An admin has manually assigned a guard to the incident
  • The incident has been acknowledged and someone is on the way

Cards in this column represent ongoing situations with an assigned responder. They should not remain here indefinitely. If an incident in Dispatched has not progressed in several hours, it may need to move to Attention or be resolved.

Attention

Incidents that require further review or have stalled. This column is used for:

  • Incidents that need admin follow-up before they can be resolved
  • Situations where the initial response is complete but the record needs verification
  • Cases where additional information or a decision is required

An admin reviews whether the description accurately reflects what happened, whether the severity rating is correct, and whether any photos or notes need to be added before the incident can be closed.

Resolved

The final state. Incidents here have been closed. The record is complete and forms part of your incident history.

Cards in this column represent completed work. They are the source data for the Analytics section.

Board columns showing incident cards across Incoming, Dispatched, Attention, and ResolvedClick to expand

Working with Incident Cards

Each card on the board displays a summary: the incident title, type, severity badge, time reported, and current status. Emergency and panic-style incidents carry a red highlight with an EMERGENCY label. Cards that need manual follow-up use a REQUIRES ATTENTION label.

Moving Cards Between Columns

Admins and Owners can drag and drop cards between columns to update their status. Guards and Clients cannot move cards.

Opening the Incident Detail Panel

Click any card to open its full detail panel. This panel is where you take action. It contains:

  • Description. The full incident narrative as reported.
  • Location. Address and GPS coordinates with a map preview.
  • Reporter. Name and role of the person who filed the report.
  • Timestamps. When the incident was created, last updated, and (if applicable) resolved.
  • Guard Assignment. Shows the assigned guard, or provides an assignment interface if no one has been assigned yet.
  • Comment Thread. Notes exchanged between admins and guards about this specific incident.

Below the details, a row of action buttons determines what happens next.

Incident Details panel open over board showing description, location, action buttons, and guard assignment sectionClick to expand

Available Actions

ActionWhat it doesResulting column
Assign GuardLets an admin manually select and assign a guard to respond from the assignment sectionCard moves to Dispatched
EditOpens the incident form to modify severity, type, description, or locationCard stays in current column
Mark ResolvedCloses the incident as handled and verifiedMoves card to Resolved
PublishMakes the incident visible to client-facing viewsKeeps the incident in its current workflow state
All Emergency DetailsOpens the extended panic/emergency panel from the detail modalPanel opens over current view
False AlarmDismisses the incident as a non-eventCloses the incident

How Incidents Move Through the Lifecycle

The four columns form a pipeline. Every incident enters from the left and exits on the right. The specific path depends on the incident's nature and severity.

Standard incident path: Incoming > Dispatched (guard assigned) > Resolved

Incident requiring follow-up: Incoming > Dispatched > Attention (needs review) > Resolved

Panic alert path: Incoming > Dispatched (guard assigned) > Resolved

False alarm path: Incoming or Dispatched > Resolved (marked as False Alarm)

Cards never move backward by default. If a resolved incident reopens (e.g., the situation recurs), a new incident should be created with a reference to the original.

Board with arrows showing incident flow direction from Incoming through Dispatched and Attention to ResolvedClick to expand

What the Operations Board Does NOT Do

  • No auto-escalation. Incidents do not automatically move between columns after a timeout. All movement is manual (drag-drop by Admin+).
  • No auto-assignment. The system does not automatically assign the nearest guard. An admin selects and assigns guards manually from the detail panel.
  • No "Escalate" action. There is no dedicated escalate button or escalation status. If an incident needs more attention, an admin drags it to the Attention column.

Use this workflow at the start and throughout each shift to maintain control of your operations board.

Start of Shift (First 5 Minutes)

  1. Open the Security Operations Board.
  2. Set the time filter to Last 24 Hours and severity to All Severities.
  3. Check the Incoming column first. If any cards are present, open each one and assess whether immediate action is needed.
  4. Scan the Dispatched column. Identify incidents that have been in progress for more than two hours. These may need follow-up.
  5. Review the Attention column. Complete any verifications left by the previous shift so these incidents can be closed.

During the Shift

  1. Keep the board open or visible on a secondary monitor. New incidents appear automatically.
  2. When a new card appears in Incoming, open it immediately. For emergency cards, use the red Emergency Info button on the card or All Emergency Details inside the modal to inspect device status and GPS accuracy before assigning a guard.
  3. Assign guards from the detail panel. Use the map view to identify the closest available team member, then assign them manually.
  4. As incidents are handled, move them through the columns: Incoming > Dispatched > Resolved (or via Attention if review is needed).
  5. Add notes to the comment thread on each incident as events develop. These notes become part of the permanent record.

End of Shift

  1. Verify that no incidents are stuck in Incoming or Dispatched without an assigned guard.
  2. Brief the incoming operator on any open items in the Attention column.
  3. Ensure all resolved incidents from your shift have been properly documented.
Resolved column showing completed incident cards with resolved status and Emergency Details buttonsClick to expand

Operational tip: The Security Operations Board is most effective when it stays open throughout your shift. It provides the most complete real-time view of what is happening, what needs attention, and what has been handled.