> For the complete documentation index, see [llms.txt](https://help.tillit.cloud/tillit/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tillit.cloud/tillit/getting-started/setup.md).

# Set up a Site & Assets

{% hint style="info" %}
At this point, it's not crucial to spend too much time on naming conventions, as these can always be adjusted later. The main goal is to initiate the process and become acquainted with TilliT
{% endhint %}

## <mark style="color:blue;">Login to TilliT</mark>

If you haven't already done so, then log into TilliT. Need help doing so? See the [Login to TIlliT](#login-to-tillit) page to find out how.

## <mark style="color:blue;">Site & Assets</mark>

### Create a Site

A site is a location where goods or services are produced or being processed. You can have more than one Site.

**Go to Settings -> Asset Hierarchy -> Sites -> Create**

<figure><img src="/files/FoougRiFQ2iryWuHjhHR" alt=""><figcaption></figcaption></figure>

### Create an Asset Class

**Go to Settings -> Asset Hierarchy -> Asset Class -> Create**

<figure><img src="/files/CzzSU5PyhOR4UkILzlaN" alt=""><figcaption></figcaption></figure>

### Create an Asset

An asset refers to anything that we want to control digitally in the context of production and supply chain management.

**Go to Settings -> Asset Hierarchy -> Assets -> Create**

<figure><img src="/files/yeFzqUGjL6cTAXNzOhpC" alt=""><figcaption></figcaption></figure>

After clicking on Create,fill in the necessary information and link the asset with the appropriate Asset Class created above and Site.

<figure><img src="/files/UmAqWjf81ZyVo0lP83qt" alt="" width="420"><figcaption></figcaption></figure>

## <mark style="color:blue;">Materials</mark>

### Add a Material Group

**Go to Settings -> Material Definition -> Material Groups -> Create**

A material group can be a category of raw materials, or a category of finished products. For example: "Ingredients" for any material that acts as an ingredient for a product, or "Finished Goods" for finished products.

<figure><img src="/files/DGeNlUe9ONcPJfEH9jDq" alt=""><figcaption></figcaption></figure>

### Add a Material

**Go to Settings > Material Definition > Materials -> Create**

Materials refer to the physical elements necessary for producing manufactured goods and are consumed during the process.

<figure><img src="/files/PF0HqduaZN3jNPYJkMuG" alt=""><figcaption></figcaption></figure>

They can also encompass the resulting product of a series of procedures, such as a finished item. Fill out the necessary fields.

<figure><img src="/files/BtRXiKueS3NXrUNe9nJg" alt="" width="419"><figcaption></figcaption></figure>

### Next steps

**Excellent**! The next step is to create an order for the asset and material.

{% content-ref url="/pages/LmC9gD8xqNsxxoarww41" %}
[Set up an Activity](/tillit/getting-started/trigger-activity.md)
{% endcontent-ref %}


---

# 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://help.tillit.cloud/tillit/getting-started/setup.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.