> 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/settings/account-management/collections.md).
# Collections
Collections organize your assets and link people, locations, and categories to create meaningful connections across your resources. You can create, rename, or delete custom collections to keep your data structured, while standard collections remain protected from deletion. You can add custom fields to existing collections, create new collections, and create links between collections to establish new connections.
## Collection types
Collections organize data to support workflows. Two types of collections are supported:
* **Dynamic collections** support real-time tasks and manage active, task-oriented data that needs frequent updates. Dynamic collections adapt in real time, reflecting the latest information based on user actions and selections within the workflow. \
For example, a dynamic collection might track equipment assignments, where each item (laptop or phone) is assigned to a person and updated as it is checked out or returned. Similarly, users can manage inventory tracking, or maintenance schedules, ensuring they stay current as tasks progress.
* **Supporting collections** don’t drive tasks but enable smooth workflows by storing the stable data on which dynamic collections rely. They include reference points like locations, client profiles, and room information, which dynamic collections reference to asset tracking. \
For example, an employee directory in a supporting collection helps users quickly assign resources to individuals by offering an easy selection list during the assignment.
Together, dynamic and supporting collections keep workflows efficient. Dynamic collections manage live tasks while supporting collections offer the background information essential for the assignment of assets. Users determine whether a collection is dynamic or supporting based on the collection's role in their workflow.
The following table describes collection types based on example workflows:
| Example | Dynamic Collection | Supporting Collection |
| -------------------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Equipment Assignment** | Tracks the assignment status of items such as laptops and phones, updating as items are checked out or returned. | Lists employees, providing a reference for assigning equipment to individuals. |
| **Maintenance Scheduling** | Manages maintenance records for vehicles or machines, showing completed and upcoming service dates. | Provides details on locations, such as the buildings and rooms where maintenance activities may occur. |
***
## Standard collections
Every Asset Panda Pro module contains a starter set of collections for **People**, **Locations**, **Categories**, and **Assets** being tracked.
{% hint style="info" %}
* These collections cannot be deleted.
* The **Assets**, **People**, and **Location** collections can be renamed based on your business needs.
{% endhint %}
* **Assets**: This collection contains all tracked assets.
* **People**: This collection can be used as an employee directory for the module. Users can assign assets that are pulled from this collection. Users can add whatever information they would like to capture about an employee. Eventually, the People collection will also combine employee records and users who have access to the module within one area.
* **Location:** This collection is not required but is available. By using the text combination formula data type, users can combine the hierarchy of their locations into one table.
* **Categories**: Categories is a customized collection that groups related assets and includes customizable fields that can be linked and filtered according to your needs. See [Manage categories](/settings/account-management/collections/categories.md).\
This collection cannot be renamed or deleted.
Users can add custom fields to these collections, create new collections, and create links between collections.
***
## Create a collection
There is no limit to the number of collections that you create within a module.
You can create a collection manually or you can import data to create a new collection. Before importing data, you must create a spreadsheet that includes the fields and records to include in the collection and then save the spreadsheet with the collection name as the file name.
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. To create a new collection manually:
1. Click **Create** and then select **Collection.** The **New collection** page is displayed.
2. Click **Create** under **New empty collection**.
3. Enter the **Collection name**.
4. Click **Create**. The collection is added to the module.
5. Add fields to the collection to gather record data. See [Fields](/settings/account-management/fields.md).
3. To create a new collection based on pre-configured data:
1. Click **Create** and then select **Collection.** The **New collection** page is displayed.
2. Click **Import** under **Import from Excel**. The Create Collection from Spreadsheet page is displayed.
3. Click **Browse** to select the spreadsheet to import. The collection will be named based on the selected file.
4. Click **Create Collection**. The collection is built with fields based on the spreadsheet data and displayed in the application.
4. To limit the records displayed, [filter the collection](#delete-collection).
5. To save the field and filter selection to a custom view, click **Save view**. See [Saved views](/settings/account-management/saved-views.md).
***
## Create linked collections
You can create links between collections by pulling fields from other collections into the current collection. This enables you to support parent-child collection situations such as the following:
* **Room locations**: Campus - Building - Room
* **Warehouse Inventory locations**: Aisle - Shelf - Position - Box
* **Geographic locations**: Country - Region - State - City
1. [Create collections](#create-a-collection) for each of the levels you want to support.
2. In the first child-level collection (for example, Buildings), click :circle-plus: to add a new field.
3. [Add fields from other collections](/settings/account-management/fields.md) to the collection.
4. When adding records to the collection, select values from the linked collection fields to build links between the records. For example, you can select the building associated with a room to link the building and its associated campus to the room.
{% embed url="" %}
***
## Rename a collection
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. In the module pane, hover over the collection to rename, click  , and then select **Edit**. The **Edit collection** page is displayed.
3. Enter the new **Collection name** and then click **Save**.
***
## Edit a collection
1. In the navigation pane, select 
**Settings** > **Account Management**.
2. Expand the appropriate account and module, and then click **Manage** in the **Collections** tile. The list of collections is displayed.
3. To hide a collection from view, click **Hide collection**  in the collection row.
4. To enable depreciation, select **Depreciation**. See [Depreciation](/maintain-records/depreciation.md).
5. To enable reservations for collection records, select **Reservations**. See [Reservations](https://prohelp.assetpanda.com/settings/account-management/pages/E6bRW1c2eC0Ud4vPRMbz#id-1.-overview).
6. To edit the fields for the collection:
1. Click **Fields**. The **Fields** page is displayed.
2. [Edit field settings](/settings/account-management/fields.md#edit-field-settings).
3. Click **Save layout**.
***
## Filter a collection
You can apply a filter to limit the records displayed for the collection.
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 filter records.
3. Click :filter:. The **Filter by** pane is displayed.
4. Select the **Field name** to filter the collection records.
5. Select the **Operator** to compare the field values.
6. Enter the **Value** to determine the records available to the collection field.
7. To specify multiple filter criteria, click **Add more** and then repeat steps 4-6.
8. If multiple conditions are specified, select an option to determine whether **All** or **Any** of the conditions must be met to enable the record to be displayed.
9. Click **Apply**.
***
## Delete a collection
{% hint style="danger" %}
Deleting a collection permanently removes all data within it and cannot be undone.
{% endhint %}
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. Hover over the collection to rename, click  , and then select **Delete**. The **Deleting collection** page is displayed.
3. Enter the name of collection to confirm its deletion.
4. Click **Yes, Continue**.
---
# 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/settings/account-management/collections.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.