> This page is for Self-Hosted, version v3.0 (default).
> For other versions, use one of these documentation indexes:
> - v3.0 (default): https://docs.nvidia.com/run-ai/self-hosted/v3.0/llms.txt
> - v2.26: https://docs.nvidia.com/run-ai/self-hosted/v2.26/llms.txt
> - v2.25: https://docs.nvidia.com/run-ai/self-hosted/v2.25/llms.txt
> - v2.24: https://docs.nvidia.com/run-ai/self-hosted/v2.24/llms.txt

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/run-ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/run-ai/_mcp/server.

# Workload Assets

NVIDIA Run:ai [workload](/run-ai/self-hosted/documentation/workloads-in-nvidia-run-ai/workloads) assets are preconfigured building blocks that simplify the workload submission effort and remove the complexities of Kubernetes and networks for AI practitioners.

Workload assets enable organizations to:

* Create and reuse preconfigured setup for code, data, storage and resources to be used by AI practitioners to simplify the process of submitting workloads
* Share the preconfigured setup with a wide audience of AI practitioners with similar needs

<Note>

**Note**

* The creation of assets is possible only via API and the NVIDIA Run:ai UI.
* The submission of workloads using assets, is possible only via the NVIDIA Run:ai UI.

</Note>

## Workload Asset Types

There are four workload asset types used by the workload:

* [Environments](/run-ai/self-hosted/documentation/workloads-in-nvidia-run-ai/assets/environments)\
  The container image, tools and connections for the workload
* [Data sources](/run-ai/self-hosted/documentation/workloads-in-nvidia-run-ai/assets/overview)\
  The type of data, its origin and the target storage location such as PVCs or cloud storage buckets where datasets are stored
* [Compute resources](/run-ai/self-hosted/documentation/workloads-in-nvidia-run-ai/assets/compute-resources)\
  The compute specification, including GPU and CPU compute and memory
* [Credentials](/run-ai/self-hosted/documentation/workloads-in-nvidia-run-ai/assets/credentials)\
  The secrets to be used to access sensitive data, services, and applications such as docker registry or S3 buckets

## Asset Scope

When a workload asset is created, a [scope](/run-ai/self-hosted/documentation/platform-management/manage-ai-initiatives/adapting-ai-initiatives-to-your-organization#scopes-in-an-organization) is required. The scope defines who in the organization can view and/or use the asset.

<Note>

**Note**

When an asset is created via API, the scope can be the entire account. This is currently an experimental feature.

</Note>

## Who Can Create an Asset?

Any subject (user, service account, or SSO group) with a [role](/run-ai/self-hosted/documentation/platform-management/authentication/roles) that has permissions to **Create** an asset, can do so within their scope.

## Who Can Use an Asset?

Assets are used when submitting workloads. Any subject (user, service account or SSO group) with a [role](/run-ai/self-hosted/documentation/platform-management/authentication/roles) that has permissions to **Create** workloads, can also use assets.

## Who Can View an Asset?

Any subject (user, service account, or SSO group) with a [role](/run-ai/self-hosted/documentation/platform-management/authentication/roles) that has permission to **View** an asset, can do so within their scope.