> For the complete documentation index, see [llms.txt](https://captivatehelp.newbluelive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captivatehelp.newbluelive.com/get-started/chapter-index-2.md).

# The Captivate interface

Learn the Captivate interface so you can find each panel, understand what it does, and shape the workspace around the way you run shows.

This chapter orients new operators to the main interface, in the order you’ll get to know it: build the list, choose a design, preview and edit it, monitor Program, then drill into the details. Read this section once before you start building projects; the rest of the help assumes you know the names of the main panels and areas of the screen.

**💡 TIP**

Before you build a production, it helps to know how Captivate will connect to the rest of your system — as a graphics contributor that an external switcher keys over video, or as the tool that renders the finished show. That choice drives your output and alpha settings. See [Choose how Captivate fits your production](/set-up-your-production/how-it-fits-your-production.md).

## What’s in this chapter

1. [Tour the Captivate interface](/get-started/chapter-index-2/the-playout-interface.md) — a quick orientation to the panels and the Setup and Live workspace layouts.
2. [Project List panel](/get-started/chapter-index-2/project-list-panel-and-channel-management.md) — the heart of your production: every item in the show lives here.
3. [Library panel](/get-started/chapter-index-2/library-panel.md) — where you start: find a title design and drag it into the Project List.
4. [Preview panel](/get-started/chapter-index-2/preview-panel.md) — see what the design looks like and modify its values, before anything goes on air.
5. [Program Monitor panel](/get-started/chapter-index-2/program-monitor-panel.md) — send it to the outside world and see exactly what’s live.
6. [Properties panel](/get-started/chapter-index-2/properties-panel.md) — drill down and work on the selected item’s details.
7. [Values Grid tab](/get-started/chapter-index-2/values-grid-tab-reference.md) — one particularly important Properties tab: prepare and switch between multiple variations.
8. [Channels](/get-started/chapter-index-2/channels.md) — separate show lists and program paths for more sophisticated productions.
9. [Customize Captivate’s layout](/get-started/chapter-index-2/customize-your-layout.md) — now organize what you work with: dock, float, and save panel arrangements.
10. [Top-bar status indicators](/get-started/chapter-index-2/top-bar-status-meaning.md) — rounding out the interface: CPU meters, streaming state, and the video panic button.

## Related

* [Get started — section overview](/get-started/branch-index.md) — the broader on-ramp to Captivate.
* [Control your show](/control-your-show/branch-index.md) — once you know the interface, learn how to drive it on air.


---

# 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://captivatehelp.newbluelive.com/get-started/chapter-index-2.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.