# Assets
This documentation is based on the *FoodCrunch* use case. Please open the link below alongside this page to understand the examples.
{% content-ref url="/pages/-MSTfiNBwo8C1m-UB3WL" %}
[Introduction and Use Case](/id-02-documentation/introduction-and-use-case.md)
{% endcontent-ref %}
An asset in Squidex is a static content such as a file, a document, an image, a video or any other media file. These assets may be used along with the data in the Content area.
An example for our *FoodCrunch* user case could be the **Logo** for the startups.
Assets can be uploaded to the root or in folders. For example, assets of type images could be uploaded to a folder called *images*.
To create a folder clickicon (2), enter a **Folder Name** (3) e.g. *images* and click **Create** (4).
## Asset Properties
An asset has properties and some of these properties can be modified once you've uploaded the asset.
Properties such as **Name**, **Slug**, **Tags** and **Metadata** can be added and/or modified. Assets can also be protected from anonymous download by checking the **Protected** box. This makes the asset private, a token must be used to download it directly.
{% hint style="info" %}
All assets uploaded are public by default.
{% endhint %}
---
# Agent Instructions: 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:
```
GET https://docs.squidex.io/id-02-documentation/concepts/assets.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.