Promoting a Policy to Enforce
A HYPR AgentPass™ policy in Observe mode changes nothing. It only records what it would have done. Promoting it to Enforce is when it starts to block requests, hold them for approval, or cut a model's reply short, for every agent and user in its scope. This page covers the check before promotion, the step itself, and the way back.
Changing a policy's state needs Policies: Edit. Admin can promote any policy. Operator and Supervisor can promote the policies they own, those whose Owner field names them.
Check Before You Promote
Open the rule's decisions: on Policies, click Details on the rule's row, and open the Decisions tab. You can also open Activity → Policy decisions, and set Policy: to the rule. Then work through these checks.
| Check | How | Why it matters |
|---|---|---|
| It catches what you meant | Would deny or Would wait rows appear for the traffic the rule is about. Read the condition each one matched, and open a few requests | A rule with no Observe matches does nothing once enforced, either |
| It catches nothing else | Look through the last 7 days for requests you did not mean to stop. Filter by connector, user or condition | Every one of those requests becomes a blocked or held request on promotion |
| Its message reads well | Read the policy's message as the person who will receive it | A blocked agent or user sees the policy's name and this message, never the condition |
| It wins where it should | Look for another enforcing rule that blocks or holds the same traffic at a lower priority number | The first enforcing block or hold decides, so only its message is shown |
| Someone can approve | For REQUIRE_APPROVAL, confirm the agents in scope have a supervisor | A request from a workload agent has no one to approve it, and does not complete |
Every policy can also be back-tested against the last 7 days of traffic, in the wizard's Back test step. Past runs are kept on the policy's History tab. See Back-Test It.
A rule that judges a model's reply ends that reply with a short note when it matches. On a Microsoft 365 Copilot connector, the user sees a blocked notice instead of the answer. Scope such a rule to the connector you mean before you promote it. See What a Match Does, by Kind of Traffic.
Promote
- Open Policies, a connector's Policies tab, or the policy's own page.
- Click the policy's State badge, and choose Enforcing.
- In the Change the state of “…”? dialog, click Set to Enforcing.
The policy's action applies from then on. Promotion changes only whether the action is applied, not the rule itself.
The State menu lists each state with a short description, and marks the current one current.
| State | Description in the menu |
|---|---|
| Disabled | Skipped at evaluation. Nothing is logged, nothing is enforced. |
| Observing | Matches are logged only. The policy’s action is not applied. |
| Enforcing | Matches get the policy’s action — denied or held for approval. |
The confirmation dialog shows the state you are leaving, the one you are moving to and its description. The confirm button names the new state, such as Set to Observing.
A REQUIRE_APPROVAL policy whose condition reads inference.* cannot be promoted. The gateway refuses the change, and asks you to use DENY to block, or to keep the policy in OBSERVE to record where approval would have been required. See Where Require Approval Applies.
Watch the First Enforced Decisions
Open the policy's Decisions tab. From the moment you promote, its matches read Denied or Sent for approval instead of Would deny or Would wait. The policy's decisions panel, opened from its Matches count, says when it switched, such as Switched from observing to enforcing on Thursday at 14:10.
An unexpected spike, or blocks on a tool you did not mean to reach, is the signal to roll back and narrow the rule. When someone reports that an agent was stopped, start from When a User Reports a Block.
Roll Back
The same State badge takes a policy back at any time.
| Choose | Effect |
|---|---|
| Observing | The action stops applying. Matches are still recorded as Would deny or Would wait, so you can keep tuning the rule against live traffic |
| Disabled | The policy is not evaluated at all. Nothing is enforced or recorded |
Rolling back is a safer first move than editing the condition under pressure. Set the policy to Observing, narrow the rule while it observes, then promote it again.
If the problem is a condition you changed, open the policy's History tab to see what changed and when. Then edit the condition back. See Edit a Policy.
Related
- How Policies Are Evaluated — modes, actions, priority and what a match does
- Policy Decisions — every policy's decisions, and each policy's own
- Investigating a Policy Decision — trace a decision to its request
- Redundant and Conflicting Rules — enforcing rules that stop another rule from ever running
- Approving and Denying Agent Actions — what a supervisor sees when a rule holds a request