---
title: "Examples and Use Cases"
slug: "notification-rules-examples-and-use-cases"
updated: 2026-04-13T15:28:26Z
published: 2026-04-13T15:28:26Z
canonical: "help.agilityblue.com/notification-rules-examples-and-use-cases"
---

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

# Examples and Use Cases

## Use Case 1

### Problem

A particular user would like to receive notifications similar to how the previous unassigned task notifications pool worked: they would like to receive a notification when a task is created and is not assigned to anyone right away and also receive a notification if a task is updated to not having an assignment.

### Solution

Create two Notification Rules:

1. Using the Tasks Object, Task Created Event, and one Field Condition: Task Assigned To is not assigned.
2. Using the Tasks Object, Task Updated Event, and one Field Condition: Task Assigned To is not assigned.

## Use Case 2

### Problem

A particular user would like to receive notifications for new tasks, but only if the task is not assigned to anyone right away and only if the task contains forms related to blowbacks, copying, or scanning.

### Solution

Create a Notification Rule using the Tasks Object, Task Created Event, and two Field Conditions: Task Assigned to is not assigned and Task Form is any of “Blowbacks”, “Copying”, and “Scanning”.

## Use Case 3

### Problem

A particular user would like to receive notifications whenever a portal user creates a new project or task.

### Solution

Create two Notification Rules:

1. Using the Projects Object, Project Created Event, and one Field Condition: Project Created By is a portal user.
2. Using the Tasks Object, Task Created Event, and one field condition: Task Created By is a portal user.

## Use Case 4

### Problem

A particular user would like to receive notifications whenever a task is placed on hold using a task comment, but only if that task comment is marked as an issue or question, if the matter is not an internal help desk matter, and the project tags do not contain “Testing” or “Help Desk”

### Solution

Create a Notification Rule using the Task Comments Object, Task Comment Created, and four Field Conditions: Matter is none of “Help Desk”, Task Comment Place on Hold is true, Task Comment Type is any of “Issue” and “Question”, and Project Tag is none of “Testing” and “Help Desk”.