> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/data-management/equipment.md). # Equipment Your device inventory: laptops, phones, peripherals, and anything else you assign. Link a device to a request to see model, serial number, and owner, and track its full lifecycle Equipment is your device inventory—laptops, phones, peripherals, and anything else you assign to people. **Why it matters** * Faster support: link a device to a request to see model, OS, serial number, last check‑in, and owner. * Lifecycle control: track “In service,” “Reserved,” “Outdated,” “Stolen,” etc. * Governance: keep a complete history of assignment and maintenance. **Types and fields** * Equipment types: define categories like Computer, Smartphone, Tablet, Screen, Other device. * Equipment fields: choose the attributes you track (e.g., Model, Serial number, Issue date, Lifecycle, Last maintenance date, Leasing info). Toggle field visibility as needed. **Inventory and profiles** * List: filter by type, lifecycle, owner, office location, or last contact date. Sort by any column, including equipment type, lifecycle, owner, serial number, model, office location, last report date, and last contact date. Sorting by last contact date surfaces devices that stopped reporting; sorting by owner groups everything one person holds. * Profile: view full details, ownership history, and related requests. Assign or reassign the owner from the profile, and use the available MDM actions from its menu. Actions such as lock or erase depend on your MDM, device capabilities, and permissions. **Unlocking a computer** On a computer managed by JumpCloud, Jamf, Iru or Intune, the actions menu also offers the secret the owner needs to get back in: **Recovery Key** (the FileVault or BitLocker key) and, on an Apple silicon Mac in Jamf or Iru, **Recovery Lock Password**. Siit reads the value from your MDM and either sends it privately to the person who holds the device or shows it to you once — it never lands in the request thread or an export. See [Secret codes](/request-management/secret-codes.md). **Kept in sync with your MDM** * **Office location:** if you're connected to Jamf, Microsoft Intune, Kandji, or JumpCloud, Siit maps office location from your MDM through the equipment field mapping, instead of leaving it blank for you to fill in by hand. On Jamf, Siit resolves the location from the buildings your integration already syncs. * **Status follows the owner:** assign an owner to a spare device and Siit automatically moves its status to **In service** unless you changed the status yourself in that same edit. This keeps large fleets from listing devices as "spare" when someone is already carrying them. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.siit.io/data-management/equipment.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.