> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/agency-permissions/create-a-catalog-for-a-video.md).

# Create a Catalog for a Video

Use the instructions below to create a category for videos. This is useful when you want several videos grouped together.

1. Click **Pages** and select **Catalog** from the menu at the top of the screen.
2. Click **+New Catalog**.
3. Add information about the video.
   1. **Label**: Add a label for the category. 
      1. For example, for Patient Testimonials, the label would be "Patient Testimonials" for product videos, the label could be "Product Overviews"
   2. **Path**: Add a path, all in lower case and separated by dashes. For example for a catalog called **Teeth Whitening** the path would be **teeth-whitening.**
   3. **Priority**: Set the priority. The number indicates what order the catalog will display. 1 = 1st, 2 = 2nd, and so on. 
4. Click **Create**. Once the new catalog has been created, you'll see the new category you just created.
5. Optional: Add a blurb to the category
   1. Select **Blurbs** from the navigation panel on the left.
   2. Click the green + screen and add a blurb with your preferred content.

Now you can go [add videos to the category](/docs/agency-permissions/adding-a-video.md#add-video-to-existing-category).


---

# 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://help.doctorlogic.com/docs/agency-permissions/create-a-catalog-for-a-video.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.