What’s new at InvGate Asset Management

A new template in the IGAM catalog auto-assigns a CI's location to match its owner's. Find it under "Settings > Automations > Templates," review it, and activate in one step. From v3.16 onwards on Pro and above plans.

→ You'll love it if you knew this automation was possible but never set it up because it wasn't obvious which trigger, filter, and action to combine.

You're asked to map the ERP in a Business Application. You know one server is involved. Open it, click the AI button (✨), and Asset Management surfaces everything it already knows: the owner, the connected database, the ESXi host, the web server. Accept what's relevant, discard what isn't. From v3.14 onwards on Pro and Enterprise plans.

You scan 80 serial numbers in a warehouse and paste the list into Asset Management. The new "is in list" operator returns every matching asset instantly. From there, bulk update their status, move them to a new location, or generate a document in one step. The operator works across the product: search bars, Smart Tags, Automations, Documents, and more. Supports serial numbers, hostnames, asset IDs, inventory IDs, asset names, and physical identifiers (RFID), up to 500 items at a time. From v3.15 onwards on all plans.

Your vendor sends a quote with 60 line items. Download the Asset Management template, paste in the vendor data, and upload it. All items load into the Purchase Order without manual entry. From v3.15 onwards on all plans.

Share it with a vendor to confirm an order or route it through an internal approval without leaving Asset Management. From any Purchase Order profile, download a PDF with all order details, line items, and the financial summary. From v3.14 onwards on all plans.

Configure Location access per role: a warehouse operator in Brazil sees Brazilian locations, an IT admin in HQ sees everything. The "Under" mode grants access to an entire branch of the hierarchy and expands automatically as new sub-locations are added. Existing roles migrate automatically on deploy. From v3.15 onwards on all plans.