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

# Re-analyzing Classifications

> Refresh server and skill classifications without waiting for new device scans

As your organization adds new MCP servers or skills to Runlayer, previously classified shadow discoveries may now match managed resources. The **Re-analysis** feature allows administrators to refresh classifications without waiting for new device scans.

## When to Use Re-analysis

Use re-analysis when:

* **New servers or skills added**: You've added MCP servers or published skills to Runlayer that may match existing shadow discoveries on devices
* **Connector updates**: Runlayer now has new server or skill definitions that may match existing shadow discoveries
* **Policy changes**: You want to refresh classifications after updating your organization's MCP policies

## How to Re-analyze

<Steps>
  <Step title="Navigate to Settings">
    Go to **Settings** in the Runlayer dashboard
  </Step>

  <Step title="Open MDM Configuration Tab">
    Select the **MDM Configuration** tab
  </Step>

  <Step title="Find Detect Re-analysis">
    Scroll to the **Detect Re-analysis** card
  </Step>

  <Step title="Configure Options">
    Click **Re-analyze Servers** and configure:

    * **Shadow servers only (recommended)** (default): Only re-analyze items currently classified as shadow. This is recommended for most use cases.
    * Uncheck to re-analyze all servers, including those already classified as managed.
  </Step>

  <Step title="Run Re-analysis">
    Click **Start Re-analysis** to begin. The dashboard card will display:

    * **Servers Analyzed**: Total servers evaluated
    * **Servers Reclassified**: Number of servers whose classification changed
    * **Newly Managed**: Items that changed from shadow to managed
    * **Newly Shadow**: Items that changed from managed to shadow (rare, typically indicates a deleted resource)
  </Step>
</Steps>

## Re-analysis Results

After re-analysis completes, the card displays a summary of changes:

| Metric                   | Description                                             |
| ------------------------ | ------------------------------------------------------- |
| **Servers Analyzed**     | Total number of servers evaluated during re-analysis    |
| **Servers Reclassified** | Servers whose classification changed (shadow ↔ managed) |
| **Newly Managed**        | Shadow items that now match a Runlayer-managed resource |
| **Newly Shadow**         | Managed items whose linked resource no longer exists    |

<Note>
  Re-analysis always creates an audit log entry when triggered, recording who initiated it, the filters used, and a summary of results. Additional audit log entries are created for each item that is reclassified, providing a complete trail for compliance and security review.
</Note>

<Note>
  The backend also re-classifies skills and plugins during re-analysis, but the dashboard card currently surfaces only server counts.
</Note>