Asset requests let people ask for equipment, and let admins review, approve, and hand it out, all with a record of who requested what and who approved it.
Anyone with portal access can submit a request with:
Asset type - what's needed, for example "Laptop" or "Monitor".
Justification - a short reason (10 to 500 characters).
Urgency - low, normal, or high.
A new request starts in the Pending status.
An admin with permission to manage asset requests (Owner, Admin, or Technician) reviews a pending request and either:
Approves it, moving it to Approved and ready to fulfill, or
Denies it, with an optional note, moving it to Denied.
Only pending requests can be reviewed. If two admins review the same request at the same time, only the first review is applied, the second is rejected rather than silently overwriting it.
Fulfilling an approved request assigns a real device to the person who asked for it:
Search for a device by name, asset tag, or serial number. Only devices that are Available and not already assigned to a person or team are offered.
Pick a device and confirm.
Fulfilling a request:
Assigns the chosen device to the requester and moves the device to Assigned.
Adds an entry to the device's custody history, the same history you see on the device's History tab.
Moves the request to Fulfilled.
If the requester is no longer a member of the organization, or the chosen device is no longer available by the time you confirm, fulfillment fails and nothing changes, so you can pick a different device or requester without leaving a half-completed assignment behind.
The person who submitted a request can cancel it while it's still Pending.
Every new request creates an Action Item in the admin inbox. That Action Item is resolved automatically when the request is approved and denied, cancelled, or fulfilled. Once a request is fulfilled, its Action Item links to the assigned device rather than the closed request, so the history stays useful.
Asset requests fire automation events for created, approved, denied, and fulfilled. Fulfilling a request also fires the same device-assigned event as a manual check-out. See Automations for how to build a rule on top of these.
