> For the complete documentation index, see [llms.txt](https://docs.blusapphire.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blusapphire.io/older-releases/09_casehub/events.md).

# Events

In Case-Hub, Any item in the Event Queue that you want to act on is considered an event. Events do not necessarily have to be connected to security, they could be network-related alerts, among others. Events serve as the primary action item for Analysts and Users of Case-Hub and will appear in the Event Queue as a card.<br>

## Event States

Events can exist in four different states to indicate where analysts are at in the triage process:

<table><thead><tr><th width="126">Status</th><th>Description</th></tr></thead><tbody><tr><td>New</td><td>The default state for all new events (unless acted on by an <a href="/pages/RXgyScJqUuMpm7Eehw2f">Event Rule</a> that overrides this status)</td></tr><tr><td>Open</td><td>Indicates that the event has been added to a case and is awaiting the analyst/client's input/review</td></tr><tr><td>Dismissed</td><td>State an event goes to when it has been automatically or manually dismissed</td></tr><tr><td>Closed</td><td>Indicates that the Event was worked in a case that has now been closed</td></tr></tbody></table>