> 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="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2FCXCMjvxQdfL4bTS8p6cE%2Fimage.png?alt=media&amp;token=984efb7d-b2ad-42ce-9697-b9013cb1e891" 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="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2F7WvCPmKpVEr9Wx5gcZmw%2Fimage.png?alt=media&amp;token=9180ea9c-4f56-496e-9dcf-824100cd4091" 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="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2FIXIxjTeIryyeaNjthT6e%2Fimage.png?alt=media&amp;token=fe57e933-5ec2-4903-81a8-310c1390045e" 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="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2FRw9ojzFO7Cp5CRuRqj8E%2Fimage.png?alt=media&amp;token=a47cb1c5-deed-4f11-b1f2-0c25ce50d6f3" 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="https://3821385045-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDvVEo0tfCfsP8te90e3t%2Fuploads%2FiEu4ABOp7O8jP8vl6iFt%2Fimage.png?alt=media&amp;token=d6067af1-b5df-4532-abca-d8ad4f2437ce" 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.                               |