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

# Automap Overview

> How Automap suggests source-to-field mappings for your data types, and how to read its confidence levels

## Overview

Automap suggests how your source data should map to a data type. Rather than finding each table and dragging each field by hand, you run Automap and get a ranked set of suggestions. It covers the primary source, field mappings, joins to related sources, and source filters. You review the suggestions, accept the ones you want, and save.

You can run Automap in two places:

> [card] [In the Mapping Editor](https://support.entegrata.com/data/pipeline/automap-entity.md)
>
> Run Automap on one data type from the **Automap** button in the mapping editor

> [card] [Across a Pipeline](https://support.entegrata.com/data/pipeline/automap-pipeline.md)
>
> Step through every unmapped silver data type in a pipeline, in dependency order

> [!NOTE]
>
> **Required permissions**
>
> * **Data Pipelines**: Access
> * **Manage Silver Entities**: Update
> * **Manage Production Pipelines** (for production pipelines and the main pipeline) or **Manage Dev Pipelines** (for development pipelines): Update
>
> These are the same permissions you need to [map fields](https://support.entegrata.com/data/pipeline/mapping-fields.md) by hand. See [roles and permissions](https://support.entegrata.com/administration/user/roles-and-permissions.md#feature-reference).

## What Automap Suggests

| Suggestion | What it proposes |
| - | - |
| **Primary source** | The table that best fits as the data type's primary source, with candidate primary key fields |
| **Field mappings** | For each unmapped field on the data type, a ranked list of source columns that could populate it |
| **Joins** | How to join a related source to the primary source when a suggested column lives in another table |
| **Table filters** | Filters on a source table, when enabled for your instance |

Automap suggests mappings only for active fields that aren't mapped yet. Your existing mappings stay as they are.

## How Suggestions Are Rated

Every suggestion has a confidence level. Automap bases it on several independent signals:

* **Schema expectations**: Entegrata's curated knowledge of which source tables and columns populate each standard data type field
* **Historical mappings**: mapping patterns from pipelines that are already deployed
* **Name similarity**: how closely a column name matches the field name
* **Usage frequency**: how often a table is used as a source
* **Column statistics**: profiles of the data in each column, such as null rate and uniqueness

When more signals agree on a suggestion, its confidence goes up. Suggestions backed by a schema expectation rank highest. Automap leaves out columns it can't use, such as columns with an incompatible data type and columns that are always empty or always hold the same value.

Expand the provider count on a suggestion (for example, **3 providers**) to see which signals contributed.

### Confidence Bands

Each suggestion is labeled with a confidence band:

| Band | Meaning |
| - | - |
| **High** | Strong match; usually safe to accept after a quick check |
| **Medium** | Plausible match; review before accepting |
| **Low** | Weak match; treat as a starting point |

Suggestions backed by a schema expectation show the Entegrata logo and the label **Schema expectation**. Table filter suggestions show a funnel icon.

### What Gets Applied Automatically

Automap applies its strongest suggestions for you:

* high-confidence schema expectation suggestions
* other high-confidence suggestions whose source is already on the canvas, or can be reached through a high-confidence join

Everything else waits for you to review it.

> [!NOTE]
>
> Applied suggestions are unsaved edits on the canvas, just like edits you make by hand. Nothing reaches your pipeline until you click **Save**, and you can undo any of it first. See [Saving Your Work](https://support.entegrata.com/data/pipeline/automap-entity.md#saving-your-work).

## Limitations

* Automap works on silver data types.
* Automap suggests mappings from tables already in your source catalog. If a table hasn't been collected yet, Automap can't suggest it. See [enabling resources](https://support.entegrata.com/data/collector/resources/enabling-resources.md).

## Related Topics

> [card] [Automap in the Mapping Editor](https://support.entegrata.com/data/pipeline/automap-entity.md)
>
> Run Automap on a single data type and review its suggestions

> [card] [Automap a Pipeline](https://support.entegrata.com/data/pipeline/automap-pipeline.md)
>
> Walk through every unmapped silver data type in a pipeline

> [card] [Mapping Fields](https://support.entegrata.com/data/pipeline/mapping-fields.md)
>
> Map fields by hand

> [card] [Configuring Sources](https://support.entegrata.com/data/pipeline/configuring-sources.md)
>
> Primary sources, related sources, and joins


## Related topics

- [Automap a Pipeline](https://support.entegrata.com/data/pipeline/automap-pipeline.md)
- [Automap in the Mapping Editor](https://support.entegrata.com/data/pipeline/automap-entity.md)


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