The User Incident History page provides a comprehensive list of all disturbance incidents associated with a specific user profile. Its primary purpose is to allow administrators to quickly review a person's history on the premises to understand behavioral patterns and retrieve details about past events. This article is intended for OPS-COM administrators responsible for security, dispatch, and incident management.
## Setup and Configuration This feature displays data logged through the *[Dispatch Logs](https://opscom.wiki/books/the-opscom-admin-portal/page/dispatch-logs "Dispatch Logs")* and *[Incident Reporting](https://opscom.wiki/books/the-opscom-admin-portal/page/incident-reports "Incident Reports")* 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. Detailed instructions for configuring this functionality can be found on the *[Incident Distribution](https://opscom.wiki/books/the-opscom-admin-portal/page/incident-distribution-feature "Incident Distribution Feature")* page.
## Using this Feature Administrators can use the following instructions to navigate to a user's incident history and interact with the available records. ### Accessing the History 1. Access the target user's profile using the administrative search tools. 2. Click the **Incident History** tab to view the list of associated incidents. ### Key Information Displayed The page lists all disturbance incidents the selected user has been involved in. Each entry in the list displays the following key information: - **Incident ID Number** - **Date and Time** of the incident - **Description** (A brief summary or classification of the incident type) ### Available Actions and Buttons Administrators can perform the following actions directly from the history list: - **Details:** Click the **Details** button next to any incident to navigate to the full report for that specific event, providing all logged information and officer narratives. - **Add Note:** Click the **Add Note** button to add a general, internal note to the user's main profile. This is useful for summarizing patterns or adding follow-up information related to their overall history. - **Edit/View Images:** Click the **Edit/View Images** button to securely manage the profile pictures or identification photos associated with this user.The accuracy of this page depends entirely on correct data 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. Whenever possible, attempt to get suspects to identify themselves with a government-issued ID to 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.** Checking this page first provides the full context of past events, flags potential safety concerns, and informs your 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 behavior.** For example, you might add a note stating, "Spoke with user on 2025-07-18 about repeated noise complaints." Keep in mind that notes specific to a single event should be added directly within that incident's details page instead. - **Identify repeat offenders:** **Leverage the information on this page to identify repeat issues and make informed administrative decisions.** This historical data is critical for supporting escalated actions, such as formally restricting property access or revoking parking privileges.