> 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/postlab.md).

# PostLab Classic

PostLab allows editors to collaborate on their Final Cut Pro and Premiere Pro projects, and media.

{% hint style="success" %}
PostLab Classic will be replaced by PostLab 2.0 in September 2024.
{% endhint %}

With PostLab, you work in a Team. A team can consist of editors, AEs, producers, and whoever needs to be able to access media and assets.

A Team organizes its work in Productions. Anything inside a Production is tracked by PostLab, and changes are automatically synced between Team Members. A Production contains Documents (a FCP Library, or Premiere Pro project), Tasks, Bookmarks, and more.

Each Team also has a Drive, PostLab's shared storage in the cloud. Whatever you put on Drive is made available to all other Team Members.

To get started is simple. Maybe have a look at this quick intro video first, and then, if you have more questions, dig in. Always feel free to [reach out to us](mailto:postlab@hedge.video) directly - we're standing by to help out.

{% tabs %}
{% tab title="Get Started in 10 Minutes" %}
{% embed url="<https://youtu.be/rF8VfPfajB0>" %}
From the 2020 FCPX Global Virtual Summit
{% endembed %}
{% endtab %}
{% endtabs %}


---

# 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/postlab.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.
