---
title: "Automation Rules Center"
slug: "automation-rules-center"
updated: 2026-03-23T10:20:10Z
published: 2026-03-23T10:20:10Z
---

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

# Automation Rules Center

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1748254007347.png)Automation rules allow you to automate processes by setting rule **triggers**, **conditions**, and **actions**. You can even tailor customized email notifications, mentioning specific **Panaya fields**(incl. custom fields) and including**direct links**to Panaya activities. For example, you can define a rule to send a notification email whenever new defects are created with high priority or if an owner has not been assigned.

[Embedded content](https://player.vimeo.com/video/660360702?h=d16f9d1a8c)

Here are a few examples of what can be achieved with automation rules.

- Send a notification email whenever new defects are created with high priority.
- Set a due date of today + X days for all defects created with high priority
- Assign all defects to Phillip if the defect is created without an assignee and notify Glen of the action
- A rule for empty values such as owners, releases, or due dates, that sends a notification email to the creator, recommending to populate the empty fields.
- A rule for setting a team. e.g. if a defect has been assigned to Judy, John, or David, then, the team field is updated to Group A
- A rule that sends the activity description in an email, upon the activity deletion.

**Good to Know!**

- Panaya triggers rules following human interaction within Panaya. An event resulting from a rule action cannot trigger another rule i.e. one trigger rule cannot trigger another rule
- Rules and actions order is important. Panaya executes rules and actions by the order of appearance. Panaya validates and confirms all rules by their order, then executes them once together.
- Upon an event (e.g. Defect Priority was updated), Panaya identifies all matching rule triggers and executes them once, by order.
- The emails are sent from noreply@panaya.com.

> [!WARNING]
> Note
> 
> To define automation rules, you need to be granted the Manage Custom Fields permission
> 
> Test status and step status are not supported within the Automation Rule Center.

> [!WARNING]
> Important!
> 
> The Automation Rule Center does not support conditions or actions based on the **test status**or**step status**.
> 
> This means you cannot -
> 
> - Trigger rules using the status of a test.
> - Trigger rules using the status of individual test steps.
> - Apply actions that depend on these statuses.

---

## **Configuring new rules**

1. Click on the **Settings button** ![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730345290.png)to open up the **Settings panel**
2. Select to View & Manage the **Automation Rules Center**.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730361581.png)

Rules are defined per System; if you manage multiple Systems, verify that the relevant System is selected from the drop-down list.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730372153.png)
3. Click on **Create**or **Create Rule**

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730398663.png)
4. Select the **project**from the drop-down list.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730405962.png)
5. **Set the trigger** Firstly, select the relevant**Panaya activity (entity) type** - Test, Step / Planned Run, Defect, Correction, Requirement / Feature (Level 1), User Story (Level 2), Task (Level 3). Then trigger for rule activation - for when this type of activity is **Created**, **Updated,**or **Deleted**.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730413010.png)
6. Set the **condition**. You can select from any available fields for the selected activity type. For example, we can set the condition to be the creation of a defect with no Dev Owner assigned.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730420790.png)
7. Set the **action**. You can set it to send an **email notification**, **send web requests**, **update a field value**, or **delete** the current **value**for fields.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1675592980708.png)

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730434348.png)

You can **add fields** to the email template **subject**and **body**.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730442377.png)
8. Click **OK**to save the rule.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730449162.png)

**Good to Know!**

- You can add up to 10 conditions and 10 actions.
- You can set rules as active or inactive as needed.

---

## Examples

Here are a few examples for an email notification action triggered by an automation rule.

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1641730461777.png)

![](https://cdn.document360.io/f404076c-de23-4609-848e-2dfd4ef701b0/Images/Documentation/image-1652346524243.png)