Viewing an Incident

YouThe canView getIncident screen allows OPS-COM administrators to thereview, viewedit, and manage comprehensive details of a security event. Its primary purpose is to provide a centralized hub for tracking dispatch logs, linked individuals, related vehicles, and assigned tasks associated with a specific incident. This article is intended for OPS-COM administrators and dispatch personnel responsible for incident management.

Setup and Configuration

Accessing and interacting with the View Incident screen fromrelies multipleheavily areas.on Searches,the reports,administrative linksroles fromand otherpermissions places.configured within the system.

OnceTo there,review youand canmodify viewthese somethingsettings, similarhover toover this:

System

Configuration, click Admin Management, and click Manage Roles.

Viewing Permissions

To simply view thean incident page, youan administrator must have one of the following baseline permissions:

• View All Incidents

• View Incidents - Self

  (Must

  • AND you mustalso be onethe reporter, Primary Investigator, Case Manager, part of thean following:

    • The reporter

    • Primary Investigator

    • Case Manager

    • Be on aassigned task groupgroup, that’s assigned in the tasks

    • Beor assigned directly to a task.task).

  If

The edit option is only available if you have one of the following permissions:

• Custom Permission - Open All

• Edit Incidents

• View Incidents - Self

  • AND you are the reporting admin

  • AND thean incident is Open

    locked,
  administrators

• Ifwith the incidentIncident is locked and the admin has theAdministrator permission "incident_admin" - Incident Administrator, then they can view the lockspecific reason.

  reason

• Iffor the adminlock. hasAdministrators with the permission "View/Edit Confidential Information,"Information theypermission canwill see aan additional Confidential Info section near the bottom aboveof files.the page.

  Editing Permissions

  To access the edit options for an incident, the administrator must meet one of the following requirements:

  • Possess the Custom Permission - Open All permission.

  • Possess the Edit Incidents permission.

  • Possess the View Incidents - Self permission, be the reporting admin, AND the incident must be in an Open state.

  Using this Feature

  Administrators can navigate to the View Incident screen from multiple areas in the system, including search results, reports, and active dispatch logs. Once on the page, the interface is divided into functional tabs and side buttons.

  Managing Tabs and Details

  • Dispatch LogsLogs:

    Anyone who can view the incident can view theits dispatch logs. ToClick addthe Log button to manually link a new dispatch entry, or dropnavigate dispatch logs from this incident,to the adminDispatch Logs tab to drop a log. You must have the permission “Add/Drop Dispatch Logs.” 
    Logs permission to perform these actions.

  • Linking dispatchPeople: logsUse canthis betab doneto fromassociate eitherindividuals with the dispatchincident. entryClick screenshow or from the link Log button:

    

    Dropping a log can be done from the Dispatch Logs tab. It will prompt the admin priormore to dropping the log:

    

    Linking People

    

    The show more section will show all theview extended details about a user that isn’tare not displayed on the screenprimary above:screen.

  • 

    Linking Other ItemsItems:

    LinkingUse otherthe itemsrespective suchtabs asto attach vehicles, missing propertyproperty, and violations canto alsothe beincident donerecord.

    from
  here.
  • There’s

    Related lessIncidents: informationView this section to show than with users.

    Related incidents can be viewed here.

    

    Useful for when several incidents are all related in some way. How these are linkedsee and managedconnect aremultiple doneoccurrences elsewhere.that share common elements.

    Checklists

  • SomeChecklists: incidentsCertain subcategories require a checklist to be filledcompleted out prior to closing or requestingbefore the incident can be closed. TheIf subcategoryrequired, isa whatwarning defineswill thisappear requirement:

    

    

    To view the checklist, the admin must have one of the following permissions "View All Incidents or Incident Administrator."

    Whenwhile the issue is stillopen. open, a warning will appear:

    

    Then they can fillFill out the details andto dependingproceed ifwith theyclosing the incident. You must have the rightView permission,All closeIncidents or requestIncident Administrator permission to view these checklists.

  • Use of Force Forms: If the incidentUse of Force setting is enabled (applicable for clients in Ontario), the government-mandated Use of Force forms will be closed:displayed as read-only documents on this page.

    

  Managing Tasks and assignmentAssignments

  • 

    Case Manager assignmentAssignment:

    ToAssign assign anthe incident to a casespecific manager,manager. the admin editing the reportYou must have the permission “Assign Incident To Case Manager”Manager orpermission. theyThe individual being assigned must alreadyhave beeither the case manager.

    Further to this, to be able to be the case manager, only the admins with the permission “Is Incident Case Manager”Manager or “Is Incident Shift Manager”Manager will be available.

    In the above example, Maximillion Smith is not the case manager, nor do they have the assign permission so they can only view who is assigned the case manager role.

    Primary Investigator assignment

    Similarly with Primary Investigator, the admin must meet one of the following criteria:

    • Permission: Edit Incident Taskspermission.

    • Permission:Primary Investigator Assignment: Assign a lead investigator to the case. You must have the Edit Incident Tasks, Is Incident Shift Manager

      ,
    or

    • Permission: Assign Incident To A Different Investigator permissions (or already be the case manager). The assignee must have the Be Assigned Tasks Directly permission.

    • Role: Is the case manager for this incident

    • Scenario: No Primary Investigator is selected and they have the permission Assign Incident to An Investigator

    Only admins with the permission “Be Assigned Tasks Directly” will be available.

    In the above example, Max has the permission Edit Incident Tasks and therefore can change the primary investigator.

    Editing Tasks and CommentsComments:

    IfAdd or edit tasks and their associated text. You must be the adminprimary is:

    investigator/case
    manager
    • or

      have the Permission: Edit Incident Tasks

    /

    • Permission: Is Incident Shift Manager

    permissions.

    • Role: Is the primary investigator or case manager

    They can add and edit tasks. They can also edit the text in the task.

    

    If theyou adminare does not have the permission, but isonly assigned to a task eitherwithout directlythese orbroader theypermissions, areyou partwill ofonly see the taskoption group, they get theto reassign option as indicated above.

    Use of Force Forms

    The use of force form is available for clients in the province of Ontario as this is a Government of Ontario form as indicated below. It requires the setting for Use of Force to be enabled. 
    

    On the view incident page, the use of force forms are read only. 

    

    Side Buttons & Permissions

    1. The first button is available and visible if the admin has the Open Incidents permission. It will either be in a state of open or close depending on the current open/close status.

    2. The second button can either be View, Edit, Edit Summary, or hidden. If the admin meets one of the following requirements: 

    • Permission: Custom Permission - Open All
    • Permission: Edit Incidents
    • Permission: Edit Incident Summaries

    • Permission: View Incidents - Self

      • AND you are the reporting adminit.

    Side

    Actions and Buttons

    WhatThe buttons on the buttonright does will depend on other states:

    • If the admin also has the Incident Admin permission:
      • AND the incident is open, the admin can edit the incident.
      • AND the incident is closed, the link will take the admin to the edit summary screen.
    • If the admin has the Edit Incident Summaries permission:
      • AND the incident is locked, they can edit the summary.
      • AND the incident is unlocked, they can edit the incident.
    • If the incident is open:
      • They can edit the incident.
    • If noneside of the scenariosscreen abovedynamically match,change thebased adminon isyour notpermissions able to edit this incident, nor the summary.

    3. The Distribute & Email buttons are only available to admins with the Incident Admin permission. 

    4. The download incident only requires the admin can view the incident at all.

    5. The toggling of read status will switchand the state of the readincident:

    status

    • Close/Open Incident: Toggles the state of the incident. Requires the Open Incidents permission.

    • Edit / Edit Summary / View: Depending on your permissions (e.g., Edit Incident Summaries, Incident Admin) and the state of the incident (Locked, Open, Closed), this button allows you to modify the full incident or just the summary details.

    • Distribute and Email: Allows you to share the incident report. Requires the Incident Admin permission.

    • Download: Downloads a copy of the incident. Available to any admin who has permission to view the page.

    • Toggle Status: Switches the state of the record back and forth between read and unread.

    • 6.Delete: IfAppears if the adminincident hasis eligible to be purged and the administrator possesses the Delete Incident permission,permission.

      then
    they
    can

    ---

    see

    Best Practices and Considerations

    • Audit Permissions Regularly: Organizations should strictly control editing and deletion permissions to maintain the nextintegrity button.of incident reports and preserve accurate historical data for legal or security audits.

    • IfComplete theChecklists IncidentPromptly: canEnsure berequired deleted,checklists aare deletefilled optionout willfully appear.before Referattempting to thisclose wikian articleincident forto moreprevent detailsadministrative aboutbottlenecks Purgingand Incidents.ensure compliance with organizational reporting standards.