diff --git a/product/admin/policies.mdx b/product/admin/policies.mdx
index 97c11a7a..f357bdf3 100644
--- a/product/admin/policies.mdx
+++ b/product/admin/policies.mdx
@@ -66,6 +66,24 @@ Policies can also fire webhooks, wait until conditions are true, and more. This
 
 Each of these is created as a step in a policy rule. 
 
+### Use a policy within a rule
+
+A policy rule's outcome, or a policy's baseline, can point to another policy instead of listing out its own steps. Build a common flow once, like a security review or a manager-then-owner approval chain, and use it from every policy that needs it. Update the policy you're pointing to, and every policy that uses it picks up the change on its next request — no hunting down copies.
+
+For example, a rule could say: "If the requester is in Engineering, use the Security review policy. Otherwise, use the Standard approval policy."
+
+To point a rule or the baseline at another policy, select **Use a policy** as the action, then choose the policy.
+
+<Note>
+A policy you point to must be the same type (request, review, or revoke) as the policy pointing to it. You can chain up to five policies deep, and C1 rejects cycles or self-references when you save.
+</Note>
+
+A few things to know about how this behaves:
+
+- **The policy locks in when a task is created.** C1 resolves the full chain at that point and snapshots it onto the task, so editing a policy you point to only affects future requests, not tasks already in progress.
+- **You can see the routing.** A task's audit log shows which policy each step came from, and where a matching rule sent the request.
+- **You can't delete a policy that's in use.** If another policy points to it, C1 blocks the deletion and names the policy that's still pointing to it.
+
 ## Get agent help building policies
 
 <Warning>
@@ -132,7 +150,7 @@ In the **If this condition matches:** box, choose how to form your policy rule:
    - Use the **Expression** field to to compose a [CEL expression](/product/admin/expressions) that describes the membership rule.
 </Step>
 <Step>
-In the **Then perform this action:** section of the rule, select an automatic action (the exact actions vary by policy type) or **Execute a workflow** to wait for a condition to be met or assign the task to a reviewer workflow (see below).
+In the **Then perform this action:** section of the rule, select an automatic action (the exact actions vary by policy type), **Execute a workflow** to wait for a condition to be met or assign the task to a reviewer workflow (see below), or **Use a policy** to [point this rule at another policy](/product/admin/policies#use-a-policy-within-a-rule) instead of building steps inline.
 
    If necessary, click **Add step** to add additional actions or workflows to the rule.
 </Step>
@@ -142,7 +160,7 @@ Repeat the **Add rule** process, adding as many conditional rules as needed. If
    Remember, for best results place more specific rules before less specific rules.
 </Step>
 <Step>
-Edit the [baseline rule](/product/admin/policies#the-baseline-rule). The baseline rule can be set to take an automatic action (the exact actions vary by policy type), or to assign the task to reviewers, as described below.
+Edit the [baseline rule](/product/admin/policies#the-baseline-rule). The baseline rule can be set to take an automatic action (the exact actions vary by policy type), assign the task to reviewers as described below, or [use a policy](/product/admin/policies#use-a-policy-within-a-rule) to point it at another policy.
 </Step>
 <Step>
 Click **Save**.
diff --git a/product/glossary.mdx b/product/glossary.mdx
index dd534b64..ef4bbbb3 100644
--- a/product/glossary.mdx
+++ b/product/glossary.mdx
@@ -125,7 +125,10 @@ A server an AI agent connects to over the Model Context Protocol (MCP) to call t
 A rule set on an access profile that automatically creates enrollment or unenrollment requests for users who meet — or no longer meet — defined criteria such as department, job title, or manager. Membership automates access changes when users join, leave, or move between teams without requiring manual requests. See [Access profile](/product/glossary#access-profile) and [Enrollment](/product/glossary#enrollment).
 
 #### Policy
-A reusable rule set that defines a process for requesting, reviewing, or revoking access. Policies can contain instructions such as who a certain task should be routed to, as well as instructions on sending notifications, triggering webhooks, conditional routing, and much more. 
+A reusable rule set that defines a process for requesting, reviewing, or revoking access. Policies can contain instructions such as who a certain task should be routed to, as well as instructions on sending notifications, triggering webhooks, conditional routing, and much more. See [Policy reference](/product/glossary#policy-reference).
+
+#### Policy reference
+A policy rule or baseline set to the **Use a policy** action, which points to another policy of the same type instead of defining its own steps. Policy references let a common flow, such as a security review or an approval chain, be reused across every policy that needs it. See [Policy](/product/glossary#policy) and [Task](/product/glossary#task).
 
 #### Profile attribute
 A piece of information about an application account that is pulled in from an application, and that can be used to scope UAR campaigns or build policies. See [Account](/product/glossary#account).