> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/managing-adoption-assets-with-the-asset-library.md).
# Managing adoption assets with the Asset library
The Asset library provides a centralized, application-level repository for storing and reusing images and PDF files across Digital Adoption content in the Nexthink platform.
The library is shared across users, meaning any user with access can view and use all available assets, helping reduce duplication and simplify asset management.
***
## Accessing the Asset library
To access the Asset library, navigate to the main menu, then select **Applications** > **Manage application assets**.
{% hint style="info" %}
Access to the Asset library is controlled at the component level. There are no [permissions](/user-guide/administration/account-management/roles.md#roles-permissions) at the individual asset level.
{% endhint %}
***
## Using the Asset library
Use assets uploaded to the library in [Nexthink Adopt](/user-guide/adopt.md) guides and supported settings without hosting files externally.
### Managing assets
The Asset library offers the same list management capabilities as other content lists in Nexthink. You can:
* Import new assets
* Use the search bar to locate assets by name
* Add and manage tags
* Filter assets by origin, tags and file type
* Preview supported assets
* Export assets
* Delete assets
These capabilities apply to all assets stored in the library.
### Filtering the asset list
Use the filters at the top of the list to narrow it to the assets you want to work on. Filter by:
* **Origin**: How the asset was added.
* **Tags**: The tags assigned to the asset.
* **Type**: The file type of the asset.
Refer to [Filtering capabilities](/getting-started/navigating-the-web-interface.md#navigatingthewebinterface-filteringcapabilities) for more information.
### Uploading assets
The Asset library supports uploading the following asset types:
* Images (JPEG, PNG, GIF, TIFF or SVG) with a maximum file size of 5 MB
* PDF files with a maximum file size of 7 MB
File type availability depends on where the asset is used. For example, media guides support only PDF files, while other guides may support images and PDF files.
To upload an asset:
1. Select **Import** from the top right.
2. Choose an image or PDF file from your device.
* You can select multiple files, which will be uploaded one at a time.
3. Select **Done**.
{% hint style="info" %}
Once uploaded, the asset becomes available to all users who have access to the Asset library.
{% endhint %}
### Using stored assets
Assets stored in the Asset library can be reused for:
* Adopt guides (walkthroughs, tooltips, and media)
* Custom logos used in the [Theme settings](/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md#customizing-the-adopt-theme-for-the-selected-application) under **Adoption settings** for applications
Using assets from the library avoids the need to host files externally or reupload the same file multiple times.
***
## Asset visibility and permissions
The Asset library does not support granular permissions per asset.
* All assets are visible to all users who have access to the Asset library.
* You cannot restrict access to specific assets for specific users.
{% hint style="warning" %}
Assets stored in the Asset library are currently not secured.
{% endhint %}
***
RELATED TOPICS
* [Applications](/user-guide/applications.md)
* [Guide creation & management from Nexthink Applications](/user-guide/adopt/guide-creation-and-management-from-nexthink-applications.md)
* [Guide content development from in-app Guides Editor](/user-guide/adopt/guide-content-development-from-in-app-adopt-editor.md)
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.nexthink.com/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/managing-adoption-assets-with-the-asset-library.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
