> 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-classic/drive/bookmarks.md).

# Bookmarks

Apart from connecting Drive directly from the sidebar in PostLab, there's also the option to do so within each Production. Doing so gives you a range of features, all built around Bookmarks.

Bookmarks are, well, bookmarks. They allow you to designate a folder anywhere on Drive, give it a name, and make it obvious to team members where you have stored certain files they might need for that production.&#x20;

![](/files/-MHLklUzFSWlOcQSX_J3)

By default, a Bookmark inherits its name from the folder it points to. Renaming is easy: just double-click or right-click, and select Rename:

![](/files/-MHLlO2947gVp_69Ta5M)

### Pinning

Bookmarks can be pinned. Pinning downloads and keeps the contents of a folder in cache at all times, until unpinned. Pinning is useful when your connection isn't fast enough to stream your media from the cloud.&#x20;

{% content-ref url="/pages/-MHSN0qghYEOcyjDEgjm" %}
[Pinning](/postlab-classic/drive/pinning.md)
{% endcontent-ref %}


---

# 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.hedge.video/postlab-classic/drive/bookmarks.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.
