> 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/server-properties/event-defaults.md).

# Event Defaults

### Introduction

Site item events can be individually linked to Action Plans. These individual settings take priority over the site-wide default settings.

Site item events can also be set up to use the default Action Plan ("Use Default"). In this situation Command Centre references this Event defaults option and uses the Action Plan set here.

If an Action Plan is assigned to an Event Group, all Event Types in that group will default to the group Action Plan, unless overridden at the Event Type level within that group.

### Procedure

1. Open the **Command Centre Server Properties** window. [How?](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/server-properties/opening-the-server-properties-window.md)
2. Click the **Event Defaults** tab.

   All available Event Groups are displayed.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-537fae66cab8a67adc1ce66bd166c606f9b3ad14%2Fevntdefault.png?alt=media)
3. Highlight the Event Group/Type you want to set the Action Plan.

   The edit box is then enabled. This box displays the set Action Plan for the selected Event Group/Type.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-13e0dc6257ee6840ff4a161f5e0628cefb6701a4%2Fapedit.png?alt=media)

   **Note:** The default Action Plan for the 'Unit on Door Tampered' Event Type (under the 'Tamper' Group) is **Log an event**. Command Centre will display a 'Unit on Door Tampered' event whose source is a door, when an associated reader or door sensor goes into a tamper state.

   This event can be configured as an alarm here instead so that these alarms will display elsewhere in Command Centre as being against the door, (e.g. if a site only has doors on their Site Plans they will show against the door. Note that if the associated reader or sensor is also on the Site Plan the alarm will show against them as well).

   If your site only requires this functionality against specific door(s), this can be configured on the **Event Response** tab of the Door(s) concerned instead.
4. Click the drop-down menu list box to display the available Action Plans. Select the required Action Plan.
5. Click **OK** to exit and save your changes.

   Click **Cancel** to exit without saving your changes.

   Click **Apply** to save your changes and stay in this window.


---

# 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/server-properties/event-defaults.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.
