---
title: Signal Routing Rules (RULE)
slug: solutions/signal-routing-rules-rule
docTags: 
createdAt: 2026-03-04T10:37:48.487Z
---

**Signal Routing Rules** control how signals are routed to playbooks. Each rule is a **record** (for example, RULE-29) that you can open, edit, and enable.

**Routing Rule Management dashboard**

The primary place to manage routing rules is the **Routing Rule Management** dashboard. The dashboard shows all rules in a table ordered by **Rule Order** (ascending). Rule order is **unique** and evaluated like firewall rules: the **first matching rule** runs, so order matters.

From the dashboard you can:

- **Reorder rules:** Use the **drag handles** (stack of dots) in the **Order** column to drag and drop rules into the desired order. Reordering changes which rule runs first when multiple rules could match.
- **Open the rule record:** Click the **ID** column icon (open-in-new view) or the **Edit** (pencil) icon to open the rule record and change conditions, playbook, or description.
- **Open the associated playbook:** Click the **Associated Playbook** link to open the playbook that runs when the rule matches.
- **Enable or disable a rule:** Use the **Enabled** toggle for each row. Rules are inactive when disabled; only enabled rules evaluate and trigger playbooks.
- **Edit a rule:** Click the **Edit** (pencil) icon to open the rule record in a slider or view so you can modify conditions, **Rule Application**, **Selected Playbook**, or other fields.
- **Delete a rule:** Use the **Delete** (trash) icon to remove a rule. Use with care; deletion cannot be undone from the UI.

Use **Add New Rule** on the dashboard to create a rule, or **Apply** to save order changes after reordering.

1\) Open **Signal Routing Rules**

- Navigate to **Application Records** -> **Signal Routing Rules** or open the **Routing Rule Management** dashboard to view and manage all rules.
- Open an existing rule via the dashboard **Edit** icon or by opening it from the application list.

2\) Core fields

- Rule identity: Rule Name, Description, **Rule Order**, rule-uuid.
- Logic: Conditions, Target, **Rule Application**.
- Execution: **Selected Playbook**, **Status**, **Records Matched**.
- **Audit**: Created by, Last updated by, First Created, Last Updated, History.

2a) Tabs

- Rule: Define conditions and rule application, and associate a playbook.
- History: **Review** routing rule changes over time.
- **Support**: **Run** the rule manually against pending signals and view **Records Matched**.

2a) Rule validation

- Use **Records Matched** to confirm rule behavior.
- **Rule Order** is unique per rule; keep order intentional so the first match wins.

Admin tips

- Manage rules from the **Routing Rule Management** dashboard for a clear view of order and status.
- Keep **Rule Order** intentional so the first matching rule fires as expected.
- Use **Records Matched** to validate expected behavior.

Commonly used fields

- Rule Name, Description, **Rule Order** to identify the rule.
- Conditions and **Rule Application** to define matching logic.
- **Selected Playbook** and **Status** to control execution.
- **Records Matched** to verify effectiveness.

### Associate a Playbook

On the **Rule** tab, set **Associated Playbook** or **Selected Playbook** after the record view finishes loading.

1. Configure **IF** conditions and **Rule Application**.
2. Select a playbook from the list. Only playbooks with a **Rule-Execute** **Flow Event** trigger appear. Playbooks without that trigger are not listed.
3. Apply the rule to the playbook (for example, **Apply rule to playbook**). The platform adds a **rule UUID** condition on the playbook trigger for this rule. Refresh the playbook in **Orchestration** to confirm.
4. Enable the rule when ready and monitor **Records Matched**.

To build a playbook before associating it, see [Building Routing Rule Playbooks](docId\:vEiFYG4oYWkQ3DcMMwjXi).

### Detailed Workflow

1. Start with **Conditions** that target a specific signal type or source.
2. Set **Rule Order** so higher-priority rules evaluate first.
3. Select and apply a **Rule-Execute** playbook (see [Building Routing Rule Playbooks](docId\:vEiFYG4oYWkQ3DcMMwjXi)).
4. Enable the rule when ready.
5. Monitor **Records Matched** and adjust conditions as needed.