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

# Get Started with Discover

> Create a Target, install a Collector, run your first scan, and register what you find.

Every other workflow in the Console starts from an Agent you already registered. [Discover](https://docs.vijil.ai/concepts/platform/discover.md) is the step before that: it finds the AI running in your estate.

By the end of this page you will have one [Target](https://docs.vijil.ai/concepts/discovery/target.md), one [Collector](https://docs.vijil.ai/concepts/discovery/collector.md) reporting into it, and a first inventory to read.

## What You Need

* A Vijil Console account, and membership of the team the estate belongs to.
* Collector artifacts from Vijil. They carry the engineering name `vijil-shadow`, which is why that name appears in package filenames, environment variables, and log paths.
* One machine, network, or cluster you want scanned, and the access to install software on it.

## Decide Your Targets First

A Target is a place you want looked at. A Collector is the software that does the looking.
Many Collectors can report into one Target, so a fleet of laptops is one Target with one
Collector per laptop.

Decide your Targets before you install anything. Use one per source: one for endpoints, one
per network, one per cluster, one per cloud account.

## Working With Discover

**1. Create Your First Target**

> [tab] Console
>
> Open **Discover** in the sidebar and press **+ New Scan**. If the modal shows tabs, stay on **Scan surfaces**. Press **+ Add new scan surface**, enter a name such as `laptops`, and press **Create scan surface**.
>
> The modal shows a **Scan surface ID** and an **Enrollment code**. The ID is the Target identifier you use everywhere below. The enrollment code lets your first Collectors enroll, allows any scanner kind, and expires after 24 hours.
>
> > [!WARNING]
> >
> > The enrollment code appears in full only once. Copy both values before you press **Done**.

> [!NOTE]
>
> The **New Scan** modal calls a Target a **scan surface**. Both names mean the same object.

> [!TIP]
>
> More detail on [Create and Manage Targets](https://docs.vijil.ai/owner-guide/discover/targets.md).

**2. Find It in the Console**

Open **Discover** and choose the **Targets** tab. Your new Target appears in the list with no kind, no scan, and no agents.

Click it to open the Target.

> [!NOTE]
>
> **On these screens, "Agent" means Collector.** The **Agents** count and the connection badge both refer to the scanning software installed against this Target. The Agent Registry uses the same word for an AI [Agent](https://docs.vijil.ai/owner-guide/register-agents/what-is-an-agent.md), which is a different thing.

The badge beside the title reads **No agent connected**. **Scan now** starts working once a Collector checks in.

**3. Create a Credential for Your First Collector**

If you created the Target in the Console, you already hold an enrollment code that works for 24 hours, so you can go straight to the next step. Otherwise, or if you need a scanner token, open the **Scanners** sub-tab. There are two kinds of credential.

| Credential | Use when |
| - | - |
| **Scanner token** | You install by hand: a Helm release, a virtual machine, a cloud connector. One token per Collector, revocable on its own. |
| **Enrollment code** | The install is unattended: laptops through device management, an extension pushed by policy. One code serves the whole rollout wave, and each machine registers as its own Collector. |

Choose an enrollment code for a fleet.

> [!TIP]
>
> More detail on [Install a Collector](https://docs.vijil.ai/owner-guide/discover/collectors.md).

**4. Install the Collector**

Pick the kind that matches what you want to reach.

| Kind | Install it on |
| - | - |
| **Endpoint** | The machine itself |
| **Network scanner** | A virtual machine inside the network |
| **In-cluster** | A Kubernetes cluster you already run |
| **Cloud API** | An Amazon EKS cluster, to reach managed AI |

The Target header changes to **Agent online** once the Collector checks in.

> [!TIP]
>
> Prerequisites and install steps for each kind: [Install a Collector](https://docs.vijil.ai/owner-guide/discover/collectors.md).

**5. Run Your First Scan**

Press **Scan now** on the Target.

Collectors poll every 30 seconds by default, so expect a short delay before the scan starts. Progress appears on the Target as it runs.

**6. Read What Came Back**

The **Findings** tab lists everything found across every Target, with a **Classification** column showing `AI` or `Non-AI`, and a dash where the Collector could not decide. Expand your Target's row on the **Targets** tab to see the same results split into `AI`, `Non-AI`, and `Uncertain`. Open any Resource for its evidence.

Then check what the scan could **not** reach. An empty finding list has two possible meanings: the scope is clean, or the Collector saw nothing.

> [!TIP]
>
> How to work through the list: [Review Discovered Resources](https://docs.vijil.ai/owner-guide/discover/reviewing-resources.md).

**7. Register What Matters**

Register a discovered Agent from the **Findings** tab, then supply the endpoint and credentials Vijil needs to reach it. Every [Diamond](https://docs.vijil.ai/concepts/platform/diamond.md) and [Dome](https://docs.vijil.ai/concepts/platform/dome.md) workflow then applies to it.

> [!TIP]
>
> What is eligible and why: [Register a Discovered Agent](https://docs.vijil.ai/owner-guide/discover/registering-agents.md).

## Housekeeping

* **Revoke credentials you no longer need.** Revoke both from the Scanners sub-tab. Revoking takes effect immediately.
* **Delete Targets you no longer scan.** Press the trash icon in the Target's row on the **Targets** tab. Deleting removes the Target's Collectors, enrollment codes, policies, and scan history, and cannot be undone.
* **Keep one Target per source.** Mixing sources makes findings harder to attribute.
* **Re-check blind spots after any access change.** A Collector that loses a permission still reports success, and its coverage shrinks.

## Next Steps

> [card] [Create and Manage Targets](https://docs.vijil.ai/owner-guide/discover/targets.md)
>
> Target types, credentials, and scheduling.

> [card] [Install a Collector](https://docs.vijil.ai/owner-guide/discover/collectors.md)
>
> Prerequisites and steps for each kind.

> [card] [Review Discovered Resources](https://docs.vijil.ai/owner-guide/discover/reviewing-resources.md)
>
> Work through `AI`, `Non-AI`, and `Uncertain`.

> [card] [Register a Discovered Agent](https://docs.vijil.ai/owner-guide/discover/registering-agents.md)
>
> Move a finding into the Agent Registry.


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