> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.7.0/helmut4-components/helmutco/projects.md).

# Projects

After a successful login the project management view will be loaded. Here, all projects that are assigned to the logged-in user via his group affiliation are listed in a table. The main page is an exact replica of the Project Tab from HelmutFX. For more information see: [Projects](/helmut4-releases/v4.7.0/helmut4-components/helmutfx/projects.md)

In contrast to HelmutFX, a click on the project name does not open the corresponding NLE, but the content of the project. The prerequisite for this is that the project has been previously indexed. During indexing, all information from the project file is read out and entered in the Cosmo database. This is always a snapshot. There is no possibility to create a live match. This can be done via a stream.

Folders, subfolders, assets (video / audio), as well as sequences and compositions are displayed.

![Projects view](/files/Jk5Ydcpug7h0YiV30AK6)


---

# 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.helmut.de/helmut4-releases/v4.7.0/helmut4-components/helmutco/projects.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.