> For the complete documentation index, see [llms.txt](https://docs.runway.team/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.runway.team/using-runway/app-settings/beta-testing-settings.md).

# Beta testing settings

### Navigate to Beta testing settings

1. Select an app in the top left corner from the Switcher
2. Navigate to **App Settings** by clicking the gear icon (⚙️) at the top of the Timeline sidebar
3. Click on **Beta testing** in the sidebar

### Configuring beta testing style

Choose which type of beta testing style your team will use for all releases of this app:

* **Non-blocking** - No soak period. The Beta testing step will automatically be shown as complete (green).
* **Open-ended soak** - An open-ended beta testing soak period. The Beta testing step will be marked as complete once the soak period is manually ended.
* **Time-limited soak** - Set a soak duration, in hours. The Beta testing step will be marked as complete once the soak duration has finished. (You can still manually end the soak period early.)


---

# 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://docs.runway.team/using-runway/app-settings/beta-testing-settings.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.