> For the complete documentation index, see [llms.txt](https://gitbook.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.tryprotege.com/event-feed/safe-rollout.md).

# Safe Rollout

## What this is

This page describes how to launch or change a Protege with lower risk.

## When to use it

Use it before enabling a new Protege, widening its scope, or changing its connected integrations.

## What you need first

* A working Protege
* Verified Event Feed and Audit behavior in at least one controlled test

## Steps

### 1. Start narrow

* Use one project, repo, team, channel, or equivalent boundary
* Avoid company-wide destinations for a first rollout

### 2. Test with real but safe traffic

* Use one event path you understand
* Confirm Event Feed first
* Confirm Audit second

### 3. Prepare the stop path

Know how to:

* Disable the Protege
* Pause the workflow if needed
* Repair or disconnect a broken integration
* Confirm whether removing integration permissions affects any live Proteges

### 4. Expand only after verification

Expand scope only when:

* The Protege behaves consistently
* The owner understands the failure modes
* The verification path is clear to the wider team
* Billing and usage expectations are understood for the larger rollout

{% hint style="info" %}
Safe rollout is mostly about scope control, observability, and reliable rollback. Keep those three things simple before you broaden coverage.
{% endhint %}

## How to verify

### You’re done when...

* The Protege works inside a narrow boundary
* Event Feed and Audit both confirm the intended behavior
* The owner knows how to pause or disable the workflow

## Common failures

* Turning on a broad workflow first
* Using several integrations before validating one simple path
* Expanding scope before a clean controlled test
* Disconnecting or changing an integration without checking which Proteges depend on it

## Next step

* [Security and permissions](/workspace-settings/security-and-permissions.md)
* [Troubleshooting](/event-feed/troubleshooting.md)


---

# 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://gitbook.tryprotege.com/event-feed/safe-rollout.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.