> 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/asset-acknowledgement-workflow.md). # Asset Acknowledgement Workflow The Asset Acknowledgement Workflow lets you automate the process of confirming asset ownership across your organization. When you run the workflow, employees receive a message via Slack or Microsoft Teams listing the assets assigned to them, along with a prompt to confirm or dispute ownership. All responses are tracked per device and assignee, giving you a clear picture of acknowledged, rejected, and pending assets without any manual follow-up chasing. *** ### How It Works When triggered, the workflow: 1. Looks up the assets assigned to the selected employees based on your configured asset scope. 2. Sends each employee a message in Slack or Microsoft Teams that lists their assigned assets and includes an acknowledgement prompt. 3. Captures the employee's response - approve, reject (with an optional note), or no response (pending). 4. Tracks all responses at the device and assignee level so you can monitor progress from a central view. 5. Optionally sends follow-up nudges to employees who have not yet responded. *** ### Configuring the Workflow #### Asset Scope You can control which assets are included in the acknowledgement messages using the asset scope toggle: * **MDM-managed devices only (default)** - the workflow includes only devices that are enrolled and managed through your MDM integration. * **MDM-managed devices and peripheral assets** - the workflow also includes peripheral assets (such as monitors, keyboards, and accessories) that are tracked in your inventory. Choose the scope that matches what you want employees to verify before running the workflow. #### Target Audience You can run the workflow for a specific group of employees or for everyone in your organization: * **Specific employees** - select individual employees or filter by a team, department, or attribute to target a subset of your workforce. This is useful for audits scoped to a particular group or for re-running the workflow after onboarding a new cohort. * **All employees** - run an org-wide acknowledgement campaign in a single step. #### Notification Channel Select whether acknowledgement messages are sent via **Slack** or **Microsoft Teams**. The workflow uses your existing integration for whichever channel you choose, so employees receive messages in the tool they already use day to day. #### Nudge Mechanism Enable the nudge mechanism to automatically follow up with employees who have not responded within a set period. Nudges are sent through the same channel as the original message and remind the employee to review and acknowledge their assigned assets. This removes the need for manual reminders and helps you reach a complete response rate faster. *** ### Employee Experience Each employee receives a message that: * Lists all assets currently assigned to them (based on the configured scope). * Includes an acknowledgement prompt with the following response options: * **Approve** - the employee confirms they have the listed assets in their possession. * **Reject** - the employee disputes ownership and can include a note explaining the discrepancy (for example, a device that was returned or never received). * **Pending** - no response is recorded yet; the employee has not interacted with the message. Employees respond directly within Slack or Microsoft Teams without needing to log in to any additional tool. *** ### Tracking Responses All responses are recorded at the individual device and assignee level. From the workflow results view you can see: * Which employees have acknowledged their assets. * Which employees have rejected one or more assets, along with any notes they provided. * Which employees still have pending responses. This gives you an audit-ready summary of asset ownership confirmation across your selected scope, and helps surface discrepancies that may need follow-up from your IT or operations team. *** ### Running the Workflow 1. Navigate to **Hardware Management** and open the **Asset Acknowledgement Workflow**. 2. Set the **asset scope** - MDM-managed devices only, or MDM-managed devices and peripherals. 3. Choose your **target audience** - specific employees or all employees. 4. Select the **notification channel** - Slack or Microsoft Teams. 5. Configure the **nudge settings** if you want automatic follow-ups for non-responders. 6. Review the configuration and start the workflow. Once the workflow is running, employees will begin receiving their acknowledgement messages. You can check the response tracking view at any time to monitor progress. *** ### Notes and Considerations * Employees who do not have any assets assigned to them within the selected scope will not receive a message. * Rejection notes submitted by employees are visible in the tracking view and can be used to initiate an asset recovery or reassignment process. * The nudge mechanism only contacts employees with a pending status - employees who have already approved or rejected their assets will not receive follow-up messages. * Make sure your Slack or Microsoft Teams integration is active and connected before running the workflow to ensure messages are delivered successfully. --- # 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.harmony.io/ai-agents/hardware-management/asset-acknowledgement-workflow.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.