Check-out & check-in
Checking an asset out assigns it to a person and changes its status to deployed. Every checkout and checkin is permanently logged in the asset's history.
Why use checkout?
The primary benefit of an asset management system is knowing who is accountable for each item. Checkout creates a documented chain of custody — if a laptop goes missing or gets damaged, you have a clear record of who had it and when.
It is technically possible to track which room an asset is in via the Location field. But checking out to a person creates accountability — a room cannot be held responsible if a device breaks or disappears.
Checking out an asset
Open the asset
Click the asset in the list to open its detail page. The asset must have status available. If it is deployed, check it in first.
Click Check Out
The Check Out button appears in the top-right of the asset detail page. It is hidden if the asset is not available.
Select the person
Type to search the Employees list. If the person doesn't exist yet, add them first from Assets → People.
Add an optional note
Notes appear in the checkout history — useful for context like "assigned for new hire onboarding" or "loaner while main device is repaired".
Confirm
Click Check Out. The asset status changes to deployed and the Assigned To field shows the person's name.
Checking in an asset
Open the asset
The asset must have status deployed. The Check In button is only shown for deployed assets.
Click Check In
Appears in the top-right of the asset detail page.
Add an optional note
e.g. "returned in good condition" or "returned damaged — cracked screen noted".
Confirm
Click Check In. Status returns to available and the Assigned To field is cleared.
Checkout history
Every checkout and checkin is permanently logged on the asset's detail page under History. Each entry shows:
- Action type (checkout or checkin)
- Person involved
- Date and time
- Any note added
- Who performed the action (the staff member who clicked the button)
History is never deleted, even if the person is later removed from Tether. Their name remains in the historical record.
GET /api/assets/{id}/history returns the full checkout log for an asset, useful for generating accountability reports.
Permissions required
| Action | Permission required |
|---|---|
| Check out an asset | assets.checkout |
| Check in an asset | assets.checkin |
| View checkout history | assets.view |
These can be granted independently. For example, a reception desk user could be given assets.checkout and assets.checkin without any edit or delete permissions.
Checkout via the API
http# Check out POST /api/assets/{id}/checkout Authorization: Bearer {token} Content-Type: application/json {{ "employee_id": 42, "note": "Assigned for new hire onboarding" }} # Check in POST /api/assets/{id}/checkin Authorization: Bearer {token} Content-Type: application/json {{ "note": "Returned in good condition" }}