Asset Ownership Confirmation
Asks employees to confirm the devices assigned to them, chases the ones who do not reply, and reports every acknowledgement, rejection, and silence back to IT.
- Runs on a schedule, quarterly by default
- Asks each employee to confirm the assets assigned to them
- Covers MDM-managed devices by default, configurable by asset type
- Nudges anyone who has not responded, up to a configurable limit
- Records who confirmed, who rejected and why, and who stayed silent
- Opens a ticket with the full CSV report for IT to follow up
What Asset Ownership Confirmation does
Asset Ownership Confirmation is asset attestation without the spreadsheet. On a recurring schedule - quarterly by default - it asks each employee to confirm the assets your records say they hold, nudges the ones who do not reply, and waits out a configurable response window. Everything that comes back is compiled into a CSV showing who acknowledged, who rejected and what discrepancy they reported, and who never responded, attached to a ticket for IT. Rejections are the valuable part: they are the difference between what your records claim and what people actually have.
Who Asset Ownership Confirmation is for
IT asset managers and compliance teams who have to attest that asset records are accurate, and who currently do it by email and spreadsheet.
Asset records drift the moment they are written. Devices get swapped, handed to a colleague, returned to a drawer, or left behind, and none of it reaches the inventory. The usual fix is an annual email asking everyone to confirm what they have, which means chasing non-responders by hand, collating replies in a spreadsheet, and finishing with data that was already going stale while it was collected.
How Asset Ownership Confirmation works
A cron schedule, quarterly by default and configurable per tenant. It can also be scoped to specific employees rather than everyone with assets. The workflow ships disabled and must be turned on.
- Send acknowledgement requests
Asks each employee in scope to confirm the assets assigned to them, covering the configured asset types - MDM-managed devices by default.
- Nudge non-responders
Follows up with anyone who has not replied, on a configurable interval and up to a configurable maximum, then closes the window after the response timeout.
- Compile the responses
Builds a CSV of the asset-by-asset results: who acknowledged, who rejected and the reason they gave, and who did not respond at all.
- Open the report ticket
Creates a ticket on the configured desk with the report attached, flagging that rejections may point to discrepancies worth investigating.
A per-cycle record of what employees say they actually hold, with discrepancies surfaced as rejections and non-responders listed rather than quietly counted as agreement.
Capabilities
- Scheduled attestation cycles - Runs on a cron schedule, quarterly by default, so confirmation is routine rather than an annual project.
- Automatic nudging - Chases non-responders on a configurable interval up to a configurable maximum, which is the part nobody does by hand.
- Asset type scoping - Covers MDM-managed devices by default, with the asset types in scope configurable per tenant.
- Targeted or fleet-wide runs - Can be pointed at specific employees, or left to cover everyone with assigned assets.
- Rejections with reasons - When an employee says the record is wrong, the reason is captured, so IT gets a discrepancy to investigate rather than a bare no.
- Non-responders counted separately - Silence is reported as silence rather than folded into confirmation, so the attestation means something.
- CSV report on a ticket - Every cycle produces an asset-by-asset report attached to a ticket for follow-up and record-keeping.
Main use cases
Quarterly attestation without the chasing - Asset records need periodic confirmation for compliance. The agent asks everyone, nudges the quiet ones up to three times, and hands IT a finished report - no spreadsheet, no reminder emails written by hand.
Finding the device that moved - An employee rejects the record because the laptop it names went to a teammate months ago. That rejection and its reason land in the report as a discrepancy to fix, which is exactly the drift an inventory cannot detect on its own.
Evidence for an asset audit - An auditor asks how asset records are verified. Each cycle produced a ticket and an asset-by-asset CSV showing confirmations, rejections, and non-responses, so the evidence already exists.
Integrations
| Integration | Role in the agent flow |
|---|---|
| Your connected MDM (e.g. Jamf Pro, Microsoft Intune, Hexnode, JumpCloud) | Supplies the managed device records employees are asked to confirm |
| Your connected HRIS (e.g. Workday, HiBob, BambooHR, Rippling) | Identifies the employees in scope and who to contact |
| Harmony Service Desk | Native ticketing - creates the ticket, carries the attachment, and records the outcome |
| Harmony Notifications | Delivers the alert through each recipient's preferred channel: Slack, Teams, or email |
FAQ
Through the channels Harmony already reaches them on, which for most teams means Slack or Teams. That is what makes response rates survivable compared with an email campaign.
Meet more Agents
