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

# Approval Routing Rules

> Manage conditional approval routing rules that assign chains by entity type at /fw/approval-routing.

The Approval Routing Rules screen lets administrators create and manage conditional routing rules that direct requests to specific approval chains and is available at `/fw/approval-routing`.

## Overview

This admin-only screen displays all approval routing rules loaded via `useApprovalRoutingRules`. Each rule card shows its entity type, associated approval chain (from `useApprovalChains`), and an active/inactive toggle. Rules can be created, edited, toggled, and deleted. Manage access is gated by `fw.approval_routing.manage` (`canManage` flag). Deletions require confirmation via an `AlertDialog`. The `ApprovalRoutingRuleDialog` component is used for both create and edit flows.

## Who it's for

Requires permission: `fw.approval_routing.view` (route guard). Manage actions additionally require `fw.approval_routing.manage`.

## Before you start

* Hold `fw.approval_routing.view` to access this screen.
* Hold `fw.approval_routing.manage` to create, edit, toggle, or delete rules.
* At least one approval chain must exist before creating routing rules.

## Steps

<Steps>
  <Step title="Open Approval Routing Rules">Navigate to `/fw/approval-routing`.</Step>
  <Step title="Create a rule">Click **New Rule** (visible with `fw.approval_routing.manage`) to open `ApprovalRoutingRuleDialog`.</Step>
  <Step title="Edit a rule">Click the edit icon on a rule card to reopen the dialog with existing values.</Step>
  <Step title="Toggle a rule">Click the toggle icon to enable or disable a rule without deleting it.</Step>
  <Step title="Delete a rule">Click the trash icon and confirm in the alert dialog to permanently remove a rule.</Step>
</Steps>

## Key concepts

* **Routing rule** — a conditional policy that maps an entity type and matching criteria to an approval chain.
* **Hit policy** — SME: confirm whether rules are evaluated first-match or all-match (not determinable from code).

## Related

<Columns cols={2}>
  <Card title="Forms & Workflow" icon="diagram-project" href="/fw/overview">
    Forms & Workflow core overview.
  </Card>

  <Card title="Governance & parity" icon="scale-balanced" href="/governance/index">
    Documentation coverage and governance.
  </Card>
</Columns>

<Note>
  This page documents shipped product behavior. It is not medical, legal, or
  billing advice. Verify against your organization's policies and applicable
  regulations before using it for clinical, compliance, or billing decisions.
  Protected health information (PHI) shown in the product is governed by your
  tenant's access controls and is never exposed in this documentation.
</Note>

<Accordion title="Documentation sources">
  * src/routes/fw\.tsx
  * src/cores/fw/pages/ApprovalRoutingRulesPage.tsx
  * src/platform/permissions/constants.ts
</Accordion>