> For the complete documentation index, see [llms.txt](https://easyedge.gitbook.io/easyedge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://easyedge.gitbook.io/easyedge/how-to/library/manage-asset-profiles.md).

# Manage Asset Profiles

This guide explains how to create and use Asset Profiles in EasyEdge.

Asset Profiles help you define a consistent set of Data Fields and Tags, making it easier to manage Assets across projects.

## Step 1 — Add a New Asset Profile to the Library

* Go to **Library** > **Asset Profiles**.
* Select **Add Asset Profile**.
* Add **all Data Fields** that describe your Asset.

{% hint style="info" %}
👉 ***Tip**: You can use multiple methods to create an Asset Profile. The **JiT Connector** allows you to upload manufacturer files (PDF, CSV, XLS, XML) to automatically build the data structure.*
{% endhint %}

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

{% hint style="success" %}
💡 **Strong Tip**

We recommend that **all Asset Profiles be created with all available Data Fields**.\
Manage data flow later by enabling or disabling the required **Asset Tags** or **Application Data Streams** per project.

Including every Data Field upfront ensures that you can easily activate new data flows in the future without editing the shared Asset Profile, helping maintain **consistency and standardization across all Assets**.
{% endhint %}

## Step 2 — Create an Asset from the Library

* When adding a new Asset to your Project, choose **Create from Library**.
* Select the Asset Profile that contains the full Data Fields.

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

## Step 3 — Generate Tags from Data Fields

* EasyEdge will create a full set of **Tags** from the Asset Profile Data Fields.
* Tags include **Names**, **Data Types**, and **Expressions**.

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

## Step 4 — Enable Tags for Your Project

* Enable only the **Tags** that are needed for your **Project**.
* You can later enable more Tags if required.

<figure><img src="/files/4FR3a7Mq8ORiVonEIt2g" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
👉 *Tip: If you want maximum flexibility, you can enable all **Tags** but limit which **Data Streams** are delivered to your **Application**.*
{% endhint %}

## Step 5 — Configure the Application Namespace

* In the **Application Namespace**, enable only the **Data Streams** you want to deliver.
* This keeps your application optimized and focused.

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

### Application Behavior - Data Streams

When a Data Stream is created as **enabled**, the property is created and data flow starts immediately.

* If the Data Stream is later **disabled**, the property remains in the Application, but data flow stops.
* If it is then **enabled again**, data flow will restart.

When a Data Stream is created as **disabled**, the property is **not created** in the Application.

* If the Data Stream is later **enabled**, the property will be created and data flow will start.
* If it is then **disabled again**, the property remains, but data flow will stop.

### Application Behavior – Data Streams (Summary Table)

|                                 |                             |               |                                                              |
| ------------------------------- | --------------------------- | ------------- | ------------------------------------------------------------ |
| **Scenario**                    | **Property in Application** | **Data Flow** | **Notes**                                                    |
| Created as Disabled             | Not created                 | None          | Enabling later will create the property and start data flow. |
| Enabled after being Disabled    | Created at that moment      | Starts        | Property persists even if disabled again.                    |
| Disabled after being Enabled    | Remains in Application      | Stops         | Disabling does not delete the property.                      |
| Re-enabled after being Disabled | Already exists              | Restarts      | Data flow resumes immediately.                               |


---

# 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://easyedge.gitbook.io/easyedge/how-to/library/manage-asset-profiles.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.