User - Incident History

The User Incident History page provides a comprehensive list of all disturbance incidents associated with a specific user.user Thisprofile. featureIts allowsprimary purpose is to allow administrators to quickly review a person's incident history on the premises to understand behavioral patterns orand retrieve details about past events. This guidearticle is intended for OPSCOMOPS-COM administrators.administrators responsible for security, dispatch, and incident management.

Setup and Configuration

This feature displays data logged through the Dispatch Logs and Incident Reporting modules. No special configuration is required to access the page itself, but incidents must be correctly created and explicitly associated with the user during the initial logging process for them to populate here.

Admin Side: Administrators must have the appropriate system role permissions enabled to view user profiles and access incident reports.

User Side: End-users do not have access to view internal incident history logs, notes, or dispatcher reports via the public-facing user portal.

Incidents can automatically be distributed to various departments, internal or external parties, or even local police.

IfDetailed youinstructions arefor interestedconfiguring inthis the functionality can be found on the Incident Distribution feature, please refer to this article.page.

Using this Feature

ThisAdministrators pagecan displays data that is logged throughuse the Dispatchfollowing and Incident Reporting modules. For incidentsinstructions to appearnavigate here, they must be correctly created and associated with the user during the incident logging process. No special configuration is required for the User Incident History page itself. To accessto a user's incident history,history firstand navigateinteract towith the profileavailable ofrecords.

Accessing the userHistory

you

wish
1. to

   Access review,the thentarget selectuser's the profile using the administrative search tools.

2. Click the Incident History pagetab to view the list of incidentsassociated incidents.

Key Information Displayed

Go to any user's profile, and Select the Incident History page to view the list of incidents.

The page lists all disturbance incidents the selected user has been involved in. Each entry in the list typicallydisplays includes:the following key information:

• Incident ID Number

• Date and Time of the incident

• Description (A brief descriptionsummary or typeclassification of the incident type)

Available Actions &and Buttons

Administrators can perform the following actions directly from the history list:

• DetailsDetails:: Each incident inClick the list has a Details button.button Clickingnext thisto navigatesany youincident to navigate to the full report for that specific incident,event, providing all logged information.information and officer narratives.

• Add Note ButtonNote:: Click the Add Note button to add a generalgeneral, internal note to the user's main profile. This is useful for summarizing patterns or adding follow-up information related to their overall history. (These are only visible on the administration side)

• Edit/View Images ButtonImages:: Click the Edit/View Images button to securely manage the profile pictures or identification photos associated with this user.

Warning: The accuracy of this page depends entirely on correct data entry.entry during the reporting phase. Ensure that all new incidents are accurately logged and associated with the correct users to maintain a complete and reliable history. TryWhenever possible, attempt to get suspects to identify themselves with a government issuesgovernment-issued ID ifto possible.ensure the correct profile is tagged.

---

Best Practices &and Considerations

• Review the history before interacting: Review the User Incident History before interacting with a user regarding a new complaint or disturbance. ThisChecking this page first provides the full context of past eventsevents, flags potential safety concerns, and informs your approach.approach to the situation.

• Summarize recurring issues strategically: Use the Add Note feature on this page to summarize recurring issues or document actions taken based on a user's pattern of behaviorbehavior. (e.g.,For example, you might add a note stating, "Spoke with user on 2025-07-18 about repeated noise complaints.)." NotesKeep in mind that notes specific to a single event should be added directly within that incident's Detailsdetails page.page instead.

• TheIdentify repeat offenders: Leverage the information on this page isto critical for identifyingidentify repeat issues and makingmake informed decisionsadministrative aboutdecisions. This historical data is critical for supporting escalated actions, such as formally restricting property access or otherrevoking administrativeparking actions.privileges.