---
title: "Configuring Incident Assignment Rules"
slug: "configuring-incident-assignment-rules"
updated: 2025-04-29T20:30:53Z
published: 2025-04-29T20:30:53Z
canonical: "docs.serenityops.com/configuring-incident-assignment-rules"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serenityops.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring Incident Assignment Rules

**Assignment rules** in Serenity ensure that incidents are automatically routed to the correct EHS group as soon as they’re reported — enabling faster response times and reducing administrative overhead.

---

## Default Assignment Rule: By Establishment

Out of the box, Serenity uses a simple but effective rule:

**Assign the incident to the EHS group defined on the related establishment.**

This ensures that every incident is immediately directed to the appropriate team based on where it occurred.

To make this work correctly:

1. Navigate to Establishments center or My Organization > Establishments
2. Navigate to each **Establishment record**
3. Make sure the **“EHS Group”** field is populated with the correct assignment group
4. Keep establishment-to-group mappings up to date as your organization evolves

💡If no EHS Group is defined, incidents reported at that establishment will remain **unassigned**.

---

## Advanced Assignment Rules (Optional)

Organizations with more complex routing needs can work with the **Serenity support team** to configure **custom if/then-style rules**.

💡 Example: “If incident category = 'Chemical Spill' → assign to HazMat Response Group”

To request custom rules, contact your Serenity support or customer success representative.

---

## 🚧 Coming Soon: Self-Service Assignment Rule Builder

We’re currently working on a **self-service rule builder**, which will allow **EHS Admins** to:

- Define new routing rules
- Create conditional logic using form fields
- Manage group assignments without opening a support ticket

This tool will be part of the **Incident Settings** page and will make routing logic more flexible and scalable for growing organizations.

---

## ✅ Best Practices

- Keep your **Establishment records** up to date and ensure all have an assigned **EHS Group**
- Use **groups** instead of individuals to reduce the need for constant reassignment

Document any custom logic internally for future reference and audits