Introduction to Policies
A Policy is a collection of rules that apply to specific Services or endpoints. Only one Catalog Policy exists, and it applies to all Services in the catalog. The Catalog Policy can contain multiple rules. Each rule has an Always use Catalog rule checkbox that determines whether the Catalog rule overrides the same type of rule set at the Service or endpoint level. With the Always use Catalog rule checkbox:
- Cleared: Rules set at the Service and endpoint override the Catalog Policy rule.
- Selected: The Catalog Policy rule overrides any Service or endpoint Policies that contain the same rule.
For example, an IP restriction rule might have different values at the Catalog, Service, and endpoint levels. Unless you select the Always use Catalog rule checkbox for that rule in the Catalog Policy, the endpoint rule applies.
The Policies tab shows rules that take precedence in a blue box and overridden rules in a red box. The following example shows a crossed-out Inbound TLS rule in the Service Policy because the Inbound TLS rule in the Catalog Policy has Always use Catalog rule selected:

The Policy Catalog has two places to create Policies:
- The Catalog Policy entry creates or modifies the Policy that applies to all Services in the catalog. For the steps, refer to Create a Catalog Policy.
- New Policy adds a Policy that you can later associate with a Service or endpoint. For the steps, refer to Create a Policy.
Both open the Policy builder:

The Policy builder categorizes rules by their type and shows the general order in which they apply during the request and response. For example, authentication and authorization follow validation. Some rules, such as request transformation, retries, and client throttling, don't strictly run in the order in which they appear. The Policy builder toolbar also has Add account, which creates an account for an outbound rule. For how outbound rules use accounts, refer to Accounts in rules.
The first five request rule categories, Validate through Transform, hold the inbound rules and apply to all requests. The outbound category applies only to requests to external endpoints, as described in Request execution flow. The following topics describe the available rules by category and provide some common use cases: