> For the complete documentation index, see [llms.txt](https://help.clause9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.clause9.com/files/how-to-files/shortcuts-to-folders-or-files.md).
# Shortcuts to folders or files
It comes in handy to have your most used folders or files as favourites – this allows you to access them more swiftly!
## Creating a favourite
In order to add a folder or file as a favourite, do the following:
* Go to *Browse files*
* Select the file you intend to add as a favourite and find the *Add favourite* button on the bottom of the navigation menu on the left-hand side of your window
* Give the shortcut a name
* Click *Save favourite*
It will now appear as a shortcut on the same menu on the left. The shortcut will also be available when narrowing down a search by location in the *Assemble Document* mode.
## Deleting favourites
In order to remove a favourite, open the personal settings menu by clicking your name in the upper right corner of your window. In the drop-down menu, choose *Favourites*.
Alternatively, you can access this settings menu by clicking *Preferences* on the same drop-down menu and by then navigating to *Favourites* on the toolbar at the top of the window.
Here, you can remove a favourite by clicking the trash bin icon next to the intended favourite.
---
# 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.clause9.com/files/how-to-files/shortcuts-to-folders-or-files.md?ask=&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.
