> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/data-library/asset-register/create-and-manage-assets-in-the-asset-register.md).

# Create and Manage Assets in the Asset Register

From the Asset Register dashboard, you can view, add, classify, and manage both auto-discovered and custom assets. The dashboard is split into two primary views:

* **Auto-discovered assets** (Infrastructure, Staff Devices, Code Repositories, People)
* **Custom assets** (Manually added assets like on-premise servers, backup devices, etc.)

This guide walks you through the key dashboard actions you can perform in each view.

***

### View Auto-Discovered Assets

1. Go to **Apps → Asset Register**.
2. Use the following tabs to explore different categories of discovered assets:
   * **Infrastructure**
   * **Staff Devices**
   * **Code Repositories**
   * **People**

Each tab provides a list of associated assets along with metadata like:

* Asset name or identifier
* Classification status
* Owner details
* Source (e.g. AWS, GitHub, Rippling)
* Date added

{% hint style="info" %}
These fields are populated automatically via connected integrations.
{% endhint %}

***

### Filter and Sort Assets

* Use column filters and sort options to refine the list of assets in any tab.
* Examples:
  * Filter Infrastructure assets by *Classification: Production*
  * Sort Staff Devices by *Date Added* or *Owner*

***

### Add a Custom Asset Individually

1. Navigate to the **Custom assets** tab.
2. Select **Add more custom assets → Add asset individually**.
3. Fill in the required fields:
   * *Asset ID*
   * *Asset Name*
   * *Asset Group*
   * *Added On* (date)
   * *Classification* (In Scope or Not In Scope – optional)
   * *Owner* (optional)
   * *Notes* (optional)
4. Click **Add Asset** to complete.

{% hint style="info" %}
Use this method for one-off additions or new physical/logical assets.
{% endhint %}

***

### Bulk Upload Custom Assets

1. Navigate to the **Custom assets** tab.
2. Select **Add more custom assets → Bulk upload assets**.
3. Click **Download template** and fill in asset details using the provided structure.
4. Click **Upload file** to import the completed template.
5. Review the records and click **Add Assets**.

{% hint style="info" %}
You can re-upload a corrected file if validation errors are found.
{% endhint %}

***

### Edit or Update a Custom Asset

* Use the **edit icon** next to a listed custom asset to:
  * Change name or owner
  * Update scope/classification
  * Add notes or correct group information

***

### Group and Categorise Custom Assets

* Use the **Group filter** at the top to view assets by category (e.g. Databases, Others).
* During asset creation, select from existing groups or create a new one.

***

### Archive or Remove Custom Assets

{% hint style="info" %}
Currently not supported directly from the UI. For removal or archival requests, contact [Sprinto Support](mailto:support@sprinto.com).
{% endhint %}


---

# 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://docs.sprinto.com/data-library/asset-register/create-and-manage-assets-in-the-asset-register.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.