Custom asset types and fields
Hardware and Software types are included by default. Add types for network equipment, peripherals, or licenses. Each type has independent Text area, Date, and Dropdown fields that can be required and reordered.
Trusted by Industry-Leading Companies
The problem
“An asset list tells you what you own. A support team also needs to know who uses it, what has changed, and which tickets involve it.”
HappyFox maintains a central register of hardware and software assets. Link records to requesters and tickets so agents can use asset context without switching tools.
Details that make the workflow work.
Access controlled by asset type
Restrict a type to selected agent teams. With access control enabled, only those teams can view, create, and manage assets of that type.
Requester and group associations
Link assets to individual requesters or requester groups for shared equipment. Requester association can be disabled for types where it is not needed.
Contact visibility with clear boundaries
Enable contact visibility per asset type. Linked contacts see the asset name and display ID in the portal, without custom field values.
Lifecycle and ticket context
Update asset status as equipment moves through stock, use, repair, and retirement. Records show Pending Tickets and Recent Tickets. Optional quantity tracking records the number of units involved in a ticket.
Scheduled sync and CSV transfers
Sync asset records from Asset Panda, Google Endpoint Management, Lansweeper, Microsoft Intune, NinjaOne, or Iru. For other systems, import with the sample CSV template for the asset type. Export records and field values by type.
How it works.
Configure your register
Define asset types, fields, team access, and requester association settings.
Bring in the inventory
Connect a supported integration for scheduled sync, or import records using the CSV template for an asset type.
Assign and connect
Add records as assets are acquired. Link individual requesters or groups, then associate assets with relevant tickets.
Track changes over time
Update lifecycle fields as assets are reassigned, repaired, or retired. The Activity tab logs changes with the agent and timestamp.
Review and export
Use ticket history and the audit trail to review an asset. Export a type’s records to CSV for audits or other tools.
Frequently asked questions.
What is an asset type?
A category with its own fields and settings. Hardware and Software are included by default; admins can add types to match the inventory.
Which custom field types are available?
Text area, Date, and Dropdown. Fields can be marked required and reordered independently for each asset type.
Can I sync assets from another tool?
Yes. HappyFox integrates with Asset Panda, Google Endpoint Management, Lansweeper, Microsoft Intune, NinjaOne, and Iru for scheduled asset sync.
How do I import inventory without an integration?
Select an asset type, download its sample CSV template, populate the columns, and upload the file. Imports operate per asset type.
Can different teams manage different asset types?
Yes. Enable access control for a type and select the agent teams that may view, create, and manage its assets. Other agents cannot see that type.
Can I link assets to tickets?
Yes. Agents link one or more assets from the ticket interface. The asset record shows associated support work in Pending Tickets and Recent Tickets.
How do I record who uses an asset?
Link requesters to the asset record. For shared equipment, link a requester group. Association settings are configurable per asset type.
What can contacts see in the portal?
When contact visibility is enabled for the type, contacts see only assets linked to them, and only their names and display IDs. Custom field values are not shown.
Is there a change history?
Yes. The Activity tab records changes, the agent who made them, and the timestamp.
Can I export records and track quantities?
Export the records and field values for an asset type to CSV. When Asset Quantity on Tickets is enabled for a type, agents can record how many units are involved in a ticket.