Check in assets

Phase 1 preview — pages render fixture data only; no changes are saved.

Selected

Eligible

Blocked / skipped

Would change

Would stay as is

Batch rule: every asset is processed on its own; one failing doesn't undo the others.
Each asset is checked in on its own; assets that aren't checked out are skipped without an error.
Check-in always logs with an empty log location; license seats and (optionally) child assets follow.
Per-asset check-in emails follow the normal rules (category check-in email); there is no consolidated email.

Selected assets (1)

Asset	Current state	Verdict	Reason / note	Would become	Actions
TC-00018 Hypervisor 01	Deployed · Checked out to London HQ – Server Room (location)	Would proceed	—	Assigned to: London HQ – Server Room → — Expected check-in: — → cleared Location: unchanged

Status after check-in

Location

Default: each asset's own default location. An empty choice clears the location (legacy).

Default location

Leave each asset's default location

Also set the default location to the chosen one

Check-in date

Also check in license seats

Also move child assets to the new location

Notes

Action type	Asset	Target	Location	Note	Changed	Actions
Check-in	TC-00018	London HQ – Server Room	—	—	—

Cancel Submitting is not available in Phase 1 — this page is a UI preview.