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

# Managing rules

> Configure Tracer rules in Console with filtering, lifecycle operations, expression validation, and scope conditions.

Use the **Rules** page to create and operate Tracer decision rules. A rule combines expression logic, decision action, and optional scope.

## Accessing the Rules page

***

In the Tracer sidebar, select **Rules**. The page opens as **Fraud Detection Rules** with the inline helper **What is a Rule?**.

## Available filters

***

Use the filter bar at the top:

| Filter               | Options                                           |
| -------------------- | ------------------------------------------------- |
| **Search**           | Search by rule name                               |
| **Status**           | All, Active, Inactive, Draft                      |
| **Decision**         | All, Allow, Deny, Review                          |
| **Transaction Type** | All Types, Card, PIX, Wire, Crypto, ACH, Internal |

You can also choose items per page.

## Rule cards

***

Each card shows:

* Rule name.
* Rule status (`ACTIVE`, `INACTIVE`, `DRAFT`).
* Rule action (`ALLOW`, `DENY`, `REVIEW`).
* Description (when provided).
* Rule expression.
* Last update date.

## Rule actions

***

The action menu on each card supports:

| Action            | Behavior                                           |
| ----------------- | -------------------------------------------------- |
| **Details**       | Opens the rule side panel                          |
| **Activate**      | Moves rule to `ACTIVE`                             |
| **Deactivate**    | Moves rule to `INACTIVE`                           |
| **Move to Draft** | Available for `INACTIVE` rules; returns to `DRAFT` |
| **Delete**        | Permanently deletes rule with confirmation         |

<Warning>
  An `ACTIVE` rule must be deactivated before moving back to `DRAFT`.
</Warning>

## Creating a new rule

***

<Steps>
  <Step>
    Click **New Rule**.
  </Step>

  <Step>
    Complete the side panel fields:

    | Field           | Required | Notes                               |
    | --------------- | -------- | ----------------------------------- |
    | **Name**        | Yes      | Rule name                           |
    | **Description** | No       | Rule context                        |
    | **Expression**  | Yes      | Evaluated with real-time validation |
    | **Action**      | Yes      | `ALLOW`, `DENY`, or `REVIEW`        |
    | **Scope**       | No       | Context restrictions                |
  </Step>

  <Step>
    Click **Create**.
  </Step>
</Steps>

New rules are created in `DRAFT` status.

## Editing a rule

***

Open **Details** to edit. The Console only allows saving changes for `DRAFT` rules. Other statuses show **Only draft rules can be edited**.

## Scope

***

In **Scope**, you can add one condition per scope type:

| Scope type       | Input                                                         |
| ---------------- | ------------------------------------------------------------- |
| Account          | UUID                                                          |
| Merchant         | UUID                                                          |
| Segment          | UUID                                                          |
| Portfolio        | UUID                                                          |
| Transaction Type | Selector (`CARD`, `PIX`, `WIRE`, `CRYPTO`, `ACH`, `INTERNAL`) |
| Sub Type         | Text                                                          |

Use **Add Condition** to append conditions.

## Related

***

* [Rule engine](/en/tracer/rule-engine) - Conceptual behavior
* [Create rule](/en/reference/tracer/create-rule) - API reference
* [Update rule](/en/reference/tracer/update-rule) - API reference