> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/maintain-records/kits.md).
# Kits
Kits enable you to create groups of serialized and/or non-serialized assets to manage them as a single unit. Kits are useful when you track or issue items, such as tool sets, device bundles, or onboarding packages.
## Kit templates
Kit templates define the standard structure of a kit. You use them to build and reuse consistent kit formats across your teams. When you create templates, you specify the type and quantity of items to include and select individual assets or reference categories (for example, "3 monitors" or "2 barcode scanners").
To create a kit template, configure the layout with the Kits property type. This allows you to control how kits behave and which assets they contain.
## Non-template kits
Non-template kits support flexible asset grouping. You can use this approach if the combination of assets changes often or if you need to build a one-time bundle. You can manually add assets to a kit record by using the Kits property. This gives you the freedom to create kits based on current needs without predefined rules.
## Visibility
In asset lists, the first column shows a mix of individual assets and kits. Each record is clearly labeled as a serialized asset, a bulk asset, or a kit. This makes it easy to identify grouped items and understand how assets relate to each other.
## Create a kit
1. Perform one of the following steps to display the module pane:
* In the navigation pane, click the **Account Switcher** 
and then select the appropriate account and module.
* Click :house: to display the module pane.
2. Select the collection for which you want to create asset kits. The list of assets in the collection is displayed.
3. Select the check box for each asset to add to the kit.
4. Click **Create kit**. The kit details pane is displayed, with the selected assets listed.
5. If necessary, adjust the assets included in the kit:
* To add additional assets to the kit, click **Add**, select the assets, and then click **Add to kit**.
* To remove selected assets from the kit, click :xmark:.
6. If any of the selected assets have a specified **Category** value, specify whether to save the kit as a template:
1. To save the created kit as a template, select **Save this kit as template**.
2. Enter the **Kit template name** to configure the template. This name is applied to the **Category name** field for the kit.
7. Enter the **Name** of the kit.
8. Specify the remaining details for the kit, and then click **Save**. The selected assets are moved into the kit, which is displayed as 
in the list.
***
## Delete a kit
When you delete a kit, you can choose whether to retain the assets in the kit.
1. Perform one of the following steps to display the module pane:
* From the **Account Switcher** , select the appropriate account and module.
* Click :house: to display the module pane.
2. Select the collection containing the appropriate assets.
3. Select the check box for the kit to delete.
4. Click **Delete**. The **Deleting kit** page is displayed.
5. Perform one of the following tasks:
* To keep the child assets and delete only the container kit, click **Keep kit content**.
* To delte the kit and all child assets, click **Delete all**.
---
# 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://prohelp.assetpanda.com/maintain-records/kits.md?ask=&goal=
```
`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.