The job of this console
Keep assignments true, fulfill incoming requests, and mark returns on exit. Do not run IT from a spreadsheet beside this register.
People · Assets
Assets
Asset register assigned to employees — laptops, badges, kits — fulfilled with access requests, not a parallel CMDB chat log.
Scroll to Flowcharts. Scenario: Assign an asset to an employee.
Kit register
What the person holds, on the person file
Assets tracks kits against Employee. A request can start in Access requests; the assignment still lands here.
People → Assets
Route
/people/assets
Org flag assetsEnabled
HR Admin · Admin
Seat at the table
HR Admin and Admin. Employees see what they hold if the product shows it; they do not edit the master.
The working rhythm
Find asset or person, assign or return, sync the related access request.
Moments that bring you here
New joiner laptop. Replacement phone. Exit day. Audit of unreturned kits.
ⓘ
Not a second vendor list
Vendors and POs stay commercial. This register is assignment to Employee.
Flowcharts
1 — Assign an asset
Register or find the asset, assign to Employee.
flowchart TD
A[Open Assets] --> B[Find asset]
B --> C[Assign to Employee]
C --> D[Fulfill access request if any]
D --> E[Return on offboarding]
- 1OpenPeople → Assets.
- 2AssignEmployee is the holder.
- 3FulfillAccess request if that started it.
- 4ReturnOffboarding checklist.
Overview
Assets is the people-side register. Vendor masters and POs stay in procurement. Access requests can trigger fulfillment but are not the asset table.
How to use
1. Employee is holder
Do not assign to a project as the only owner unless the product supports it.
2. Return on exit
Offboarding tracks; this register is the assignment.
3. Serials here
Not only in a ticket comment.