> For the complete documentation index, see [llms.txt](https://docs.squidex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.squidex.io/id-02-documentation/concepts/apps.md).

# Apps

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 %}

## What is an App?

An App in Squidex is the highest level of organization for your content. An App could represent a project, a team or an application in your organization or structure. This is where the schema, actual content, assets and settings etc., live. 

<figure><img src="/files/ZxA6Mx0l67RgPoddQRSb" alt=""><figcaption><p>Apps overview in Squidex (self-hosted) or Squidex Cloud</p></figcaption></figure>

An App is made up of the following:

* A display name, description and logo to make it discoverable in the overview.
* **Schemas** to define the structure of your content.
* **Content** itself.
* **Assets** such as images, that belong to your App and are linked to your content.
* **Rules** to model business workflows.
* **Custom Workflow** definitions.
* **Collaborators** who can work on your content with roles and permissions.
* A subscription and an associated plan in the Squidex Cloud.<br>

  <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Subscriptions and plans are applicable only when using Squidex Cloud (https://cloud.squidex.io/)</p></div>

<figure><img src="/files/62nqcYRDHJzX82LFaV8A" alt=""><figcaption><p>Dashboard of an App</p></figcaption></figure>