> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/asset-management/manage-assets.md). # Review and manage assets (staff) Reception and security manage declared assets from the dashboard's **Visitor Log** and from the Guardian app: verify items on entry, set each item's status, and confirm what leaves the site on exit. Status is set by the operator rather than locked to a sequence, so you can change it directly as the visit progresses. ## Asset statuses An asset can hold any of these statuses. The dashboard shows the same definitions in the status dropdown: * **Checked In**: reception or security has validated and approved the declared asset for entry onto the premises. * **Checked Out**: reception or security has confirmed the asset's removal from the premises on exit. * **Declared**: the visitor has declared this asset on entry. Awaiting validation by reception or security. * **Left the site**: the asset left the site without being declared or validated. Review may be required. * **Still on site**: the asset was declared on entry but not checked out. It is assumed to still be on site. ## Manage assets from the dashboard Work through a visitor's assets from the **Visitor Log**: filter the log by status, then open a visitor to edit items and set each one's status. {% stepper %} {% step %} ### Open the Visitor Log Go to **Visitors → Logs**. Set the date range you want to review. {% endstep %} {% step %} ### Filter by asset status Open the **Declared Assets** column filter and select the statuses you want: **Checked In**, **Checked Out**, **Declared**, **Left the site**, or **Still on site**. The row count updates to the filtered results. {% endstep %} {% step %} ### Open a visitor's assets Click the visitor's asset chips (or the **Add assets** cell) to open the asset panel. Each card shows the item's description, identifier, notes, and status. {% endstep %} {% step %} ### Confirm details and set status Confirm each item's details, then set its **Status** from the dropdown. Use **Check-In All** or **Check-Out All** to set every item at once. {% endstep %} {% step %} ### Submit Click **Submit** to save the changes. The updated statuses appear back in the **Visitor Log**. {% endstep %} {% endstepper %} ## Check assets in (Guardian app) When a visitor arrives, reception verifies their declared assets and checks them in. 1. Open the visitor's profile and tap the **Assets In** tile. 2. Tap an asset to review its photo, description, identifier, and notes; edit any field as needed and tap **Save Changes**. 3. Set each item to **Checked In** (the toggle highlights green when set). 4. Tap **Complete Check-In** to submit. The profile reflects the checked-in count. {% embed url="" %} Walkthrough: reviewing, editing, and checking in a visitor's assets in the Guardian app. {% endembed %} {% hint style="info" %} **Note:** you can review a visitor's assets at any time, but assets can only be edited while the visitor is still on site. {% endhint %} ## Check assets out on exit As a visitor leaves, work through their declared assets and confirm what's leaving with them. The check-out runs on the reception iPad and the Guardian app. {% stepper %} {% step %} ### Reopen the profile Reopen the visitor's profile from the **Visitor Log** and tap the **Assets Out** tile. Confirm the sign-out when prompted. {% endstep %} {% step %} ### Mark each declared asset For each item, tap **Checked Out** if it's leaving with the visitor, or **Still On Site** if it isn't shown on exit. The tally updates as you go (for example, "2 Checked Out · 1 On Site"). {% endstep %} {% step %} ### Log anything undeclared Tap **Add Undeclared Asset** to record an item that wasn't declared on entry, following the usual photo and detail steps. {% endstep %} {% step %} ### Complete the check-out Tap **Complete Check-Out** to submit. The final statuses appear on the visitor's profile and in the **Visitor Log**. {% endstep %} {% endstepper %} {% embed url="" %} Walkthrough: checking a visitor's assets out on the reception iPad. {% endembed %} To correct a record, reopen **Assets Out**, change an asset's status, and submit again. Use the three-dot menu on an asset to **Edit Asset** or **Remove Asset**; a removed item moves to deleted and can be restored. Items left in **Still on site** or **Left the site** are surfaced so security can investigate. To add or capture assets onto a record in the first place, see [Declare assets](/command-centre/visitor-management-powered-by-kenai/asset-management/declare-assets.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.security.gallagher.com/command-centre/visitor-management-powered-by-kenai/asset-management/manage-assets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.