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

# Create Video Highlights

You can move directly from finding news to creating a video without leaving the meeting.

The workflow has five steps:

1. **Find:** choose one or more moments worth sharing.
2. **Refine:** adjust clip boundaries and improve each moment's context.
3. **Compose:** choose a Highlight Reel or Social Video, include the right moments, and set their order.
4. **Finalize:** review the presentation and distribution settings, then generate.
5. **Distribute:** watch the finished video, download it, and decide whether to publish or post.

Selecting a moment or generating a video does not, by itself, make the work public. Before you generate, you control that with **Auto-publish when ready** for Highlight Reels and **Post to Reels when ready** for Social Videos.

If this is your first creation, SeeGov briefly pauses before generation so you can finish your creator profile and acknowledge the Creator Guidelines. People who already have Backstage access continue immediately after setup; you are not applying for another permission.

Start with [Select and refine moments](/create-video-highlights/select-and-refine.md), or use [Create without publishing or posting](/guidance/experiment-without-publishing.md) for a safe first experiment.


---

# 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.seegov.org/create-video-highlights.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.