> For the complete documentation index, see [llms.txt](https://docs.sonoransoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonoransoftware.com/store/dashcam.md). # Dashcam Dashcam gives emergency and fleet vehicles a complete mobile-evidence workflow. It can preserve activity before and after an incident, start from manual or automatic triggers, and let authorized staff return later to review what happened from six vehicle-mounted viewpoints.
Events Dashcam incident replay and mobile evidence overview

Record the real vehicle perspective, then reconstruct and replay the incident later.

{% hint style="info" %} **Dashcam is a paid DLC for the free Events Core package.** Install Events Core once to provide the shared recording, replay, storage, and event logic required by Dashcam and other Events products. Events Core does not add a separate gameplay interface by itself. {% endhint %} ## Capture the full incident The rolling pre-event buffer helps preserve what led up to an incident, not only what happened after the record button was pressed. A recording can begin manually or from configured activity such as emergency lights, a siren, a collision, a nearby gunshot, or a speed threshold. Operators can: * Start or stop a recording from the evidence terminal, a keybind, or a command * Save the current buffer with the configured pre-event context * Add labeled evidence markers while a recording is active * See recording status, department, speed, and coordinates in the in-game overlay * Search finalized evidence by recording, vehicle, plate, department, incident, case, citation, or arrest-report information
Dashcam active recording status overlay

The compact overlay keeps the recording ID, department, speed, location, and timezone visible while the terminal is closed.

## Review from six viewpoints Each vehicle recording can be reviewed from front, rear, cabin, prisoner, left, and right views. Reviewers can play, pause, seek, skip, step through the timeline, change speed, and switch viewpoints without returning to the original vehicle. Dashcam replay reconstructs the recorded incident inside FiveM. It is not a conventional video file by default, so historic review does not depend on someone watching or streaming the camera live when the incident occurs.
Dashcam Mobile Evidence terminal with an active structured replay

Review the recorded timeline and switch among all six vehicle-mounted viewpoints.

## Manage evidence access ACE permissions and optional framework job grades control who can record, review their own or departmental evidence, add notes, classify records, lock or archive evidence, change retention, and delete unprotected records. The shipped retention policy includes separate periods for routine recordings, traffic stops, arrests, use-of-force incidents, training, and indefinite retention. ## How it works 1. An authorized driver enters an eligible vehicle. 2. A manual or automatic trigger starts a recording with pre-event context. 3. The recording captures the configured area around the moving vehicle. 4. The finalized record appears in the Mobile Evidence terminal. 5. An authorized reviewer searches for the record, opens it, and replays the incident from any of the six views. ## Requirements | Requirement | Details | | -------------- | ------------------------------------------------------------------------------------------------- | | Events Core | Free required package: [download Events Core](https://sonoran.store/packages/7606652-events-core) | | Events Dashcam | Paid DLC: [download Dashcam](https://sonoran.store/packages/7618996-events-dashcam) | | FXServer | A current FiveM server with OneSync enabled | | Permissions | ACE permissions or a supported framework job setup | | Framework | Standalone by default; ESX, QBCore, and Qbox context can be configured | | Database | No SQL database is required by the default configuration | ## Start here 1. Follow [Installation](/store/dashcam/installation.md) to install Events Core and Dashcam in the correct order. 2. Review [Configuration](/store/dashcam/configuration.md), [Vehicle Setup](/store/dashcam/vehicle-setup.md), and [Permissions](/store/dashcam/permissions.md). 3. Test manual and automatic [Recording](/store/dashcam/recording.md) in an eligible vehicle. 4. Open the finalized record and test [Playback and Evidence](/store/dashcam/playback.md). Building an integration? See the [Developer API](/store/dashcam/developer-api.md) for supported exports and lifecycle events. For help, see [Troubleshooting](/store/dashcam/troubleshooting.md) or contact [Sonoran Software support](https://support.sonoransoftware.com/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sonoransoftware.com/store/dashcam.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.