> 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/use-cases/use-case-unassign-an-asset-from-a-person.md).

# Use Case: Unassign an asset from a person

A common use case for Asset Panda Pro is unassigning assets from an employee or company.

## Typical configuration <a href="#tech-req-assign-to-a-person" id="tech-req-assign-to-a-person"></a>

Asset Panda Pro recommends the following configuration as a starting point for unassigning an asset from a person.&#x20;

### User/asset requirements

* User has access to Asset Panda Pro. See [Invite users to a module](/settings/users.md#invite-users-to-a-module).
* User can access and submit forms. See [Roles & permissions](/settings/roles-and-permissions.md).
* The asset record exists in the appropriate collection. See [Maintain records](/maintain-records.md).
* The asset status is **Assigned**.&#x20;

### Configure collections

The collections must contain the following fields. See [Fields](/settings/account-management/fields.md).

<table><thead><tr><th width="131.796875" valign="top">Collection</th><th width="147.25390625" valign="top">Field</th><th valign="top">Field Settings</th></tr></thead><tbody><tr><td valign="top"><p><strong>Assets</strong></p><p></p></td><td valign="top"><strong>Status</strong></td><td valign="top"><p>Single Select List with the following values:</p><ul><li>Available</li><li>Assigned</li></ul></td></tr><tr><td valign="top"></td><td valign="top"><strong>Assigned To</strong></td><td valign="top"><p>Pull from the <strong>People</strong> collection, with the following settings:</p><ul><li><strong>Primary Field</strong>: <strong>Name</strong></li><li><strong>Secondary Field</strong>: <strong>Location</strong></li></ul></td></tr><tr><td valign="top"><strong>People</strong></td><td valign="top"><strong>Name</strong></td><td valign="top">Text field</td></tr><tr><td valign="top"></td><td valign="top"><strong>Location</strong></td><td valign="top">Pull from the Location collection, with <strong>Primary Field</strong> set to <strong>Name.</strong></td></tr><tr><td valign="top"><strong>Location</strong></td><td valign="top"><strong>Name</strong></td><td valign="top">Text field</td></tr></tbody></table>

{% hint style="info" %}
The name of the Assets collection may differ.
{% endhint %}

### Configure a saved view

The following saved view should be configured. See [Saved views](/settings/account-management/saved-views.md).

* **Available Assets:** Filtered by **Status** *is equal to* **Available.**&#x20;

### Configure a form

A form with the following settings must exist to update the records to reflect the assignment. See [Forms that update records](/settings/account-management/forms/forms-that-update-records.md).

* **Form setup**:
  * **Form name**: Unassign From Person
  * **This form will**: Update records
  * **For**: Single record or Multiple records
  * **In this collection**: Assets
  * **Allow receipt of responses after submission & generate PDF**: Select as required
* **Form build**:
  * **Form description**: Use this form to unassign assets from a person after long-term possession.
  * **Add Field**: Assigned To
  * **Thank you message**: Edit as needed
  * **After form submission perform these actions**:
    * **Perform**: Replace
    * **Collection field**: Status
    * **Operation**: Available
* **Share**: Select as needed. See [Share](/settings/account-management/forms/forms-that-update-records.md#share).

### Configure an automation&#x20;

The following automation should be created to support the unassignment:

* **Automation Settings**:
  * **Automation Name**: Assign to Person - HR Notification
  * **Description**: Notify the HR Specialist that an asset has been returned.
* **When**:
  * **Trigger**: When a form is submitted
  * **Using**: Unassign from a person
* **Then**:&#x20;
  * **Type**: Send Notification
  * **Compose > To**: HR Specialist Email
  * **Compose > Subject**: An asset has been unassigned!
  * **Compose > Body**: An asset has been unassigned from a user.

***

### Configure a dashboard widget

The following dashboard widget should be created to display the results of the assignment:

* &#x20;**Available Assets**
  * **Widget Type**: Chart
  * **Chart Type**: Pie
  * **Chart Name**: Available Assets
  * **Chart Description**: Available Assets
  * **Module**: Appropriate module name
  * **Data Source**: Saved Views: Available Assets
  * **Field**: Status

***

## Use case example

*On Monday morning, Mary, an IT Manager, receives an email from her CEO. Tom officially retires today and will be returning his company-issued laptop. Tom must return a laptop, and Mary must ensure the return is recorded in the system.*

### Preconditions check

* **Access to Asset Panda**: Mary logs in using her IT Manager credentials.
* **Asset Assignment**: Mary confirms that a laptop is assigned to Tom.
* **Permissions**: Mary has access to submit forms and update asset records within the collection.
* **Form Access**: The Unassign from Employee Form is enabled for use.

### Laptop unassignment

1. Mary navigates to the appropriate IT Asset Management (ITAM) module in Asset Panda Pro and then selects the Assets collection.&#x20;
2. Mary filters the asset list to show only those marked as **Assigned To** Tom.&#x20;
3. Under **Forms**, Mary locates the **Unassign from Employee** form.
4. In the **Unassign from Employee** form, Mary enters the following details:
   * **Assigned To**: Clears Tom's name
   * **Status**: Available (automatically updates the record)
5. Mary reviews the details and submits the form. The **Asset Status** field shows **Available**.

***

### Automated actions

When the form is submitted, the following actions occur based on configured automations:

* A notification email is sent to HR. The email subject indicates “An asset has been returned!” and the email details that Tom has returned the laptop.
* The asset’s status changes from **Assigned** to **Available**.

***

### Dashboard and save view results

After the assignment, the following saved views and dashboards reflect the update:

* **Available Assets**: Mary can see all assets currently available, including Tom's returned laptop.
* **Manager Dashboard**: Mary’s manager can see a summary of all assigned assets, grouped by location and employee. Tom's asset is no longer visible as associated with Tom.
* **Assets by Person** and **Assets by Location**: These pie charts on the dashboard reflect the updated data.
* **Assets Assigned to Me**: When Tom logs into his Asset Panda account, he no longer sees the laptop listed.


---

# 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:

```
GET https://prohelp.assetpanda.com/use-cases/use-case-unassign-an-asset-from-a-person.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.