> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/methods-for-reusing-authored-content-classic.md).

# Methods for reusing authored content (classic)

{% hint style="info" %}
Nexthink Finder is a Windows-only desktop application whose functionality is now available within the Nexthink web interface. Nexthink can now be used directly from a browser and most functions no longer require an additional desktop application.
{% endhint %}

## Overview <a href="#methodsforreusingauthoredcontent-classic-overview" id="methodsforreusingauthoredcontent-classic-overview"></a>

A situation may arise when you’d like to share content that you have created, either in Finder or the Nexthink web interface, with others. Within a normal setup, defined as an installation with one Nexthink web interface and several connected Engines, you can create content that other system users instantly share. Some examples of this include centralized content created with Finder or [content associated to roles](/platform/user-guide/administration/account-management.md#accountmanagement-defining-user-roles).

## Manual import/export in Finder <a href="#methodsforreusingauthoredcontent-classic-manualimport-exportinfinder" id="methodsforreusingauthoredcontent-classic-manualimport-exportinfinder"></a>

Other types of content that you create in Finder are local to each Engine. To share local content:

1. Connect to the Engine, which holds the elements that you wish to share with Finder
2. Export the elements manually and then connect to the target Engine to import them back.

[This manual method](/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/manually-sharing-content-with-finder-classic.md) is also valid for exporting local or centralized content to Engines in different setups as long as dependencies are respected. For instance, to export an investigation with conditions that include a category not present in the target Engine, you must import the category beforehand.

## Publishing modules <a href="#methodsforreusingauthoredcontent-classic-publishingmodules" id="methodsforreusingauthoredcontent-classic-publishingmodules"></a>

The Nexthink web interface has its own way of sharing content among different users: administrators can [publish the modules](/platform/user-guide/custom-dashboards-classic/reusing-custom-dashboards-content-classic.md) they create and optionally assign them to roles so that other users can benefit from them. This method, however, does not let you take content from one instance of Nexthink web interface and import it into another. This latter scenario typically occurs when you have separate pre-production and production environments.

## Content packs <a href="#methodsforreusingauthoredcontent-classic-contentpacks" id="methodsforreusingauthoredcontent-classic-contentpacks"></a>

To export a coherent set of Finder and web interface elements at the same time, use content packs. A content pack groups multiple items of Finder content and the Nexthink web interface modules into a single file. For instance, if you take the previous dependency example, in the same content pack, you can include an investigation and the categories on which the investigation depends. Similarly, when exporting the Nexthink web interface modules, you would want to include the metrics and the services on which the modules depend in the same content pack. The following articles explain how to [import content packs](/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/exporting-a-content-pack-classic.md) or [make your own content packs](/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/exporting-a-content-pack-classic.md).

## Nexthink Library <a href="#methodsforreusingauthoredcontent-classic-nexthinklibrary" id="methodsforreusingauthoredcontent-classic-nexthinklibrary"></a>

Ready-made content packs are available from [Nexthink Library](https://www.nexthink.com/library). The packs in the Library are designed to provide you with customizable solutions for different IT areas: security, transformation, compliance, etc. The [method to import a library pack](/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/importing-a-content-pack-classic.md) differs from importing a content pack from a file.


---

# 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.nexthink.com/platform/user-guide/using-finder-classic/importing-and-exporting-authored-content-classic/methods-for-reusing-authored-content-classic.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.