> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/ai-agents/hardware-management/unassigned-assets-agent.md).

# Unassigned Assets Agent

The **Unassigned Assets** agent automatically scans your asset inventory and identifies active, company-owned assets that have no employee assigned to them. Instead of relying on manual audits, the agent runs on a schedule and surfaces gaps in asset ownership before they become compliance or security risks.

When unassigned assets are detected, the agent creates a structured ticket, attaches a CSV report of every affected asset, and notifies the right people - so your IT team can immediately act to reassign, retire, or investigate each item.

***

### What the Agent Does

Each time the agent runs, it checks your active company asset inventory for records with no assigned employee. If any are found, the agent:

* **Creates a ticket** containing a full CSV report of all unassigned assets
* **Populates related assets** directly on the ticket so you can review and act on each item without leaving the ticket view
* **Sends a notification** via Slack or Microsoft Teams to the desk owner, or to all admins if the desk itself is unassigned
* **Repeats automatically** on the schedule you configure, so your inventory stays continuously monitored

If no unassigned assets are found during a run, no ticket is created.

***

### Configuration Options

When setting up the Unassigned Assets agent, you can customize the following:

| Setting                | Description                                                  |
| ---------------------- | ------------------------------------------------------------ |
| **Schedule**           | How frequently the agent runs (for example, daily or weekly) |
| **Ticket Destination** | The board or queue where new tickets are created             |
| **Ticket Priority**    | The priority level assigned to each generated ticket         |

***

### Notifications

The agent uses your connected Slack or Microsoft Teams integration to send notifications when unassigned assets are found:

* If the destination desk has an owner, that owner receives the notification directly
* If the desk is unassigned or has no owner, all admins are notified instead

This ensures the right people are always alerted, regardless of how your desks are organized.

***

### Getting Started

1. Navigate to **AI Agents** in your Harmony settings.
2. Locate the **Unassigned Assets** agent under the **Hardware Management** section.
3. Enable the agent and configure your preferred schedule, ticket destination, and priority.
4. Save your settings. The agent will run automatically according to the schedule you set.

Once active, every run that detects unassigned assets will produce a ticket your team can use as a working list to resolve ownership gaps quickly.

***

### Tips

* Run the agent on a frequent schedule (for example, daily) after periods of high employee turnover or large hardware deployments to catch gaps early.
* Review the CSV attached to each ticket to get a full picture of affected assets before making reassignment decisions.
* Use ticket priority settings to align with your team's SLA expectations for resolving asset ownership issues.


---

# 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.harmony.io/ai-agents/hardware-management/unassigned-assets-agent.md?ask=<question>&goal=<user_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.