Every asset has a custodian, a location, and a movement history

With a custom field, yes — and it is worth knowing the difference. There is no grant or donor object in the product, so an asset has no native funding field. What assets do support is custom fields, so you add one called funding grant and it behaves like any other column: filterable, reportable, exportable, and available on the end-of-project disposition report. What you do not get is referential integrity — it is a label somebody types or picks, nothing validates it against a list of live grants, and nothing stops two people spelling the same donor differently. For most registers that is enough. If your funder requires an auditable link between an asset and a grant record, say so and we will scope it properly rather than let a custom field imply something stronger than it is.

Custodian clearance shows every asset issued to the person; return is recorded at handover, and unreturned items are visible before the final paycheck, not after.

They run on mobile with condition notes and photos, and they need a connection — verification is not one of the four operations that work offline. Those four are stock transfers, inventory check-out and check-in, and asset movements, so moving an asset between sites works with no signal while confirming it is still there does not. For a round at a site with no coverage, plan it for where there is coverage or expect to complete it on return.

Assets can be created from received purchase orders, inheriting supplier, cost, and grant — so the register grows from real transactions instead of manual entry.