> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Assigning Unknown Systems

> Review systems that were found but not typed, edit them in bulk and assign them to a type.

If a system answers during a scan but cannot be assigned to a type, it lands
in this list instead of the inventory. It is the step between a find and an
asset: every entry is either assigned a type or removed.

On the dashboard, the *Unknown Systems* metric with the line *Typing pending*
leads straight here.

## Information per entry

*Details* opens a display-only sidebar with four fields for each row:

| Field | Content |
| - | - |
| *Hostname* | the name under which the system reported itself |
| *Operating System* | as far as recognizable |
| *IP Address* | the reported address, marked when obtained through DHCP |
| *Detected On* | date with time |

Missing values appear as a dash.

## Editing entries in bulk

Select several rows through the checkboxes and choose *Edit Systems*: the
sidebar opens a form whose activated fields apply to every selected entry.
Whatever you do not explicitly activate stays unchanged.

<Warning>
  **Name and IP address cannot be set here** – both are excluded from bulk
  editing because they differ per system. Only shared entries are assigned:
  type, environment data and similar fields.
</Warning>

<Tip>
  Review a few entries through *Details* first – often a pattern shows up, an
  address range or a device class. Then edit by that pattern instead of row by
  row.
</Tip>

*Delete* removes the selected entries for good, after a confirmation.

<Warning>
  A deleted entry cannot be restored. Delete only what you were actually able to
  classify, or what demonstrably does not belong to your environment.
</Warning>

## What the list does not show

Two things are deliberately missing here:

* **The job that made the find.** There is no direct reference; through
  *Detected On* and the IP address, though, a find can be narrowed down
  against the [execution history](/docs/en/scan/manage-jobs#reading-the-job-detail)
  and the targets of your jobs.
* **A direct type assignment per row.** This page does not assign a single
  system to a type; only bulk editing does that.

<Tip>
  If a whole address range stays unknown, the cause usually lies with access,
  not with this list: a target that answers but cannot be signed in to delivers
  too little for a classification. Check the credentials of the job concerned
  and its [Last Scan Details](/docs/en/scan/manage-jobs#reading-the-job-detail).
</Tip>

## Related

Docusnap365 carries assigned systems as an asset from then on – it continues
with [capturing ITAM data](/docs/en/itam/manage-data).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.