---
title: "approvals rules update"
description: "Update an approval rule"
canonical: "https://pgbeam.com/docs/cli/approvals/rules/update"
last-updated: "2026-10-08T08:55:02.000Z"
---

# approvals rules update

> Update an approval rule

URL: https://pgbeam.com/docs/cli/approvals/rules/update

Replaces the rule's name, statement kinds, scope, row threshold and enabled flag. An approval request already held keeps the name it was held under.

Returns 409 when the update leaves the rule enabled while the organization has a live self-hosted data plane enrollment, for the same reason as create. Setting enabled to false is still accepted.

## Usage

## Options

Option

Description

Required

Default

`<id>`

Yes

-

`--name <value>`

Label shown to the reviewer on every approval request this rule holds. Must be unique within the project and not blank.

Yes

-

`--statement-kinds <value>`

Statement kinds the rule holds. Empty or omitted holds every kind. One of: insert, update, delete, ddl.

No

-

`--schema-name <value>`

Schema to scope the rule to. Null, empty or omitted matches every schema.

No

-

`--relation-name <value>`

Relation to scope the rule to. Null, empty or omitted matches every relation. Without a schema it matches that name in every schema.

No

-

`--min-affected-rows <value>`

Hold only statements affecting at least this many rows. Must be at least 1. Null or omitted holds every matching statement. The count is taken in a rolled-back trial run; a statement that reports no count (DDL, a batch, a data-modifying CTE) is held regardless.

No

-

`--enabled <value>`

False switches the rule off, so it holds nothing.

No

-

All global options (`--token`, `--profile`,
`--project`, `--org`, `--json`, `--no-color`, `--no-trunc`, `--debug`) are
also available on this command.

## Examples

## Output

Renders a human-readable table or detail view by default; pass `--json` for the raw API response.