---
title: "Assets"
canonical: "https://support.appfire.com/space/RM/3459318035/Assets"
format: markdown
---
Use **Assets** to maintain a registry of the systems, services, products, environments, and data that risks and Signals in the current Jira space relate to.

Assets provide context about what is affected, who owns it, and where mitigation work should happen. They can be linked to risk work items directly or through mapped Signals, and LiveRisk can use their context when generating AI estimates and treatment plans.

Open a risk register, then click the *Assets* tab.

## Prerequisites

- Your access to Assets depends on your LiveRisk permissions and asset ownership.
- If you do not have permission to manage the full asset registry, you see a partial asset hierarchy:
  - Assets you own and all assets nested beneath them are visible and editable.
  - Parent assets above the assets you own remain visible as read-only context so you can understand their position in the hierarchy.
  - Other assets in the registry are not shown.
- If no assets are assigned to you, LiveRisk displays an empty state until someone with the **Manage LiveRisk Risk Register** permission assigns you as an Asset owner.
- See **[Roles and permissions](https://appfire.atlassian.net/wiki/spaces/RM/pages/3496575012)** for details about access to asset-management actions.

## Browse and filter assets

Assets available to you are displayed in a hierarchy on the left side of the page. Depending on your permissions and asset ownership, this may be the full registry or a partial hierarchy.

If you are an Asset Owner without access to manage the full registry, parent assets may appear as read-only context above the assets you can manage.

Expand a parent asset to view the assets beneath it, or select an asset to view its details.

> ℹ️ The hierarchy is flexible, so you can structure assets in the way that best represents your organization, such as:
> ℹ️ 
> ℹ️ **Portfolio → Product → Environment**
> ℹ️ 
> ℹ️ or:
> ℹ️ 
> ℹ️ **Business service → Application → Infrastructure**
> ℹ️ 
> ℹ️ ![Asset hierarchy showing parent and nested assets in LiveRisk.](media://edaf7a68-d204-4b80-9875-85a334ca9fce)

Use the search field to find assets by name or description. You can also filter the registry by:

- **Asset type**
- **Maximum impact**
- **Data classification**
- **Environment**
- **Owner**
- **Jira space**
- **Labels**

Filters apply to the assets shown in the hierarchy.

## Create an asset

1. Click **Add asset** to create a top-level asset. To add an asset beneath an existing one, use the **+** action next to the parent asset.
2. Enter the asset details and save.
3. Select an existing asset to open its details and make changes. New and existing assets use the same fields:
  - **Name: **The name used to identify the asset.
  - **Asset owner: **The person responsible for the asset. Asset ownership also affects which assets some users can see in LiveRisk.
  - **Asset type: **Describes what kind of asset it is.
  - **Asset Max Impact: **Indicates the highest potential impact associated with the asset. Use this to capture the importance of the asset to your organization.
  - **Data classification:** Identifies the sensitivity of the data associated with the asset
  - **Environment:** Identifies where the asset operates, such as Production or another configured environment.
  - **Labels:** Use labels to add additional classifications that can help users find and filter assets.
  - **Description: **Provide a short explanation of what the asset is or what it does.
  - **Asset profile:** Use **Asset profile** to provide business and operational context about the asset. LiveRisk's AI scoring and treatment assistants can use this information when analyzing risks and generating treatment plans. Include information that can help explain: what the asset supports, why it is important, what systems or users depend on it, the potential impact of disruption, and relevant operational or security context. Do not include secrets, credentials, or other sensitive information in the Asset profile.
  - **Jira space:** Associate the asset with the Jira space where related work is managed. LiveRisk can use this information when determining where treatment work should be created.  
When all assets linked to a risk point to the same Jira space, LiveRisk can suggest that space for treatment work. If the assets point to different spaces, select the appropriate space when confirming the treatment plan.

> ℹ️ Use the description and other context fields to capture information that may help users and AI understand the asset’s purpose, importance, and potential impact.

## Reorder assets

Drag assets within the hierarchy to change their position or parent.

To move an asset to the top level, drag it to the **Drop here to make an asset top-level** area.

Reordering may be unavailable while search or filters are active.

## Delete an asset

Open the asset’s actions and select **Delete Asset**.

LiveRisk may prevent deletion when the asset is still in use. If this happens, review the reason shown and remove or update the relevant links or mappings before trying again.

## Related tasks

- **[Import and export assets](https://appfire.atlassian.net/wiki/spaces/RM/pages/3682304191)** — create or update assets in bulk using CSV or JSON, or export asset data.
- **[Use assets with risks and signals](https://appfire.atlassian.net/wiki/spaces/RM/pages/3682893856)** — map signal groups to assets, link assets to risks, and understand how LiveRisk uses asset context.