> For the complete documentation index, see [llms.txt](https://docs.hedge.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hedge.video/connect.md).

# Connect

Connect is our companion app that gives you live insight and push notifications about the state and progress of your transfers, transcodes, and archiving.

Connect is available for all licenses that are eligible for updates and support. Pro licenses automatically send their data to Connect, while non-Pro licensees must manually hook up their computers to Connect in-app.

## Dashboard

Connect offers an online dashboard, available at <https://connect.hedge.video>. Log in with either the email connected to your license key(s), or your license key itself.

## Setting Up

Connect is available in OffShoot, EditReady, and Canister. We have setup guides available for each app:

* [Connect for EditReady](https://docs.hedge.video/editready/connect.md)
* [Connect for Canister](https://docs.hedge.video/canister/features/connect.md)
* [Connect for OffShoot](https://docs.hedge.video/offshoot/features/connect.md)

## Requirements

Connect has seen several iterations in the last 10 years, and is currently on its third. That means not every application that shows a Connect panel is still functional. These are the minimum versions required for the current Connect:

* Canister 23.2
* EditReady 24.4
* OffShoot 23.2


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hedge.video/connect.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
