> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-a-dvr-system/editing-action-plans-with-dvr-cameras.md).

# Editing Action Plans with DVR Cameras

### Introduction

Operators with the “Edit Alarm Configuration” operator privilege can modify Action Plans.

### Procedure

Refer to the procedure for [Creating a new Action Plan](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/action-plans/creating-a-new-action-plan.md) for full details on how to add a DVR Camera to an Action Plan.

Note though for every trigger DVR Camera you will need a dedicated relay (output) also to communicate the trigger to the external DVR recording device.

Each dedicated relay (output) should also have a pulse time set, via the Advanced tab of the Output Property page. The pulse time may control the number of seconds of video stored after the alarm, depending on the DVR manufacturer. Alternatively, the number of seconds of pre-alarm imaging and post-alarm imaging may be configured through the DVR manufacturers software, and the Command Centre relay pulse time should be set to one second.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/external-systems/configuring-a-dvr-system/editing-action-plans-with-dvr-cameras.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
