> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/reference/playbook/toggling-protocols-per-run.md).

# Toggling protocols per run

## Two different kinds of "off"

There are two different ways to stop a protocol from applying, and they are not the same:

* **Disabling a protocol** (covered in [Enabling and disabling a protocol](/reference/playbook/creating-protocols.md#enabling-and-disabling-a-protocol)) turns it off everywhere, for every future run, until it is re-enabled. This is a persistent change to your Playbook or the firm's.
* **Opting a protocol out for a single run** leaves it enabled in the Playbook, but skips it for just the run you're working on right now. This is the tool for "I know this rule usually applies, but not to this specific client's situation this one time."

## Where the per-run toggle appears

When starting or reviewing a task, active protocols that apply to that task type are shown with an option to opt out for that run specifically - without touching their Playbook-level Active status. This is confirmed for AI Review runs, where an opt-out control appears alongside the protocols that would otherwise apply to that review.

## When to use a per-run toggle instead of disabling

Use the per-run toggle when a protocol is generally correct but doesn't fit one specific case - for example, a firm-wide threshold protocol that shouldn't apply to an unusual client this year. Use full disabling (from the Playbook) when a protocol is wrong or no longer wanted at all, for every future run.

Opting out for a single run does not change the protocol's Active/Disabled status in the Playbook - the next run defaults back to the protocol applying normally, unless it's opted out again.

## Where to check what applied to a specific run


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.filed.com/reference/playbook/toggling-protocols-per-run.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.