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

> ## Agent Instructions
> PawSQL 是一个产品：Cloud 是公网部署形态，Engine / Optimizer / Auditor / Advisor / Patroller 是同一产品的组件与交付形态，不是彼此独立的产品。 / PawSQL is a single product: Cloud is the public deployment form, while Engine / Optimizer / Auditor / Advisor / Patroller are components and delivery forms of the same product, not separate products.
> 术语以站内术语表为准：SQL 审核对应英文 SQL Review，查询重写对应 Query Rewrite，索引推荐对应 Index Recommendation；英文内容统一用 Review，不用 Audit。 / Use the site glossary for terminology: 审核 is SQL Review, 重写 is Query Rewrite, 索引推荐 is Index Recommendation; English content uses Review, never Audit.
> 引用能力范围或版本支持时以对应页面为准；标注 unknown、或 status 非 published 的内容表示尚未经产品核实，不应作为事实引用。 / Cite capability scope and version support from the corresponding page; content marked unknown, or with a status other than published, is not yet product-verified and must not be cited as fact.

# Select a Review Policy

> Choose a matching review policy when creating a review ticket: match the database engine, environment, and workflow, then verify rules, severities, and thresholds.

When creating a review ticket, pick a matching policy from the "review policy" dropdown (the interface may label it "review template"). The right policy gives comparable work a consistent standard and keeps irrelevant database or environment checks out of the result set. The definition of a policy, default and custom templates, and rule and threshold management are covered in [Rules and Quality Policy](/en/user-guide/rules-policy/).

## Goal

Choose a review policy that matches the target database engine, environment, and workflow, so comparable SQL uses a consistent standard.

## Prerequisites

Know the target database engine, version, environment, and intended review purpose before selecting a policy.

## Selection order

Evaluate candidate policies in this order:

1. Match the target database engine and version.
2. Match the environment, such as development, test, or production.
3. Match the workflow, such as developer feedback, release review, or remediation.
4. Verify ownership, visibility, and the responsible maintainer.
5. Review rule severities, parameters, and thresholds.

## Inspect the policy before use

Verify at least the following:

* supported database engines and versions;
* policy status and most recent update;
* enabled and disabled rules;
* severity assigned to each rule;
* configurable limits such as length, count, duration, or affected rows;
* documented exceptions or exclusions;
* policy scope within the current organization or project.

<Warning>
  Policies with the same display name can still differ by project, revision, or update date. For a formal review, verify the policy identity rather than relying on its name alone.
</Warning>

## If a policy is unavailable

| Symptom                        | What to check                                                     |
| ------------------------------ | ----------------------------------------------------------------- |
| Policy list is empty           | Database selection, project scope, permissions, and policy status |
| Expected policy is hidden      | Organization context and policy visibility                        |
| Rules differ from expectations | Policy revision, update date, and database version                |
| Policy cannot be edited        | Project administrator or policy-owner permissions                 |

## Expected Result

The selected policy's rules, severities, and thresholds match the target database and workflow, avoiding irrelevant checks in the result set.

## Related resources

After understanding the policy, return to [Create a Review Ticket](/en/user-guide/sql-audit/create-review-task). See [Rules and Quality Policy](/en/user-guide/rules-policy/) for creating and maintaining policies.