# Endorsement

Endorsement tells AI agents which tables to reach for first. Each table has one of three statuses, set from the **Endorsement** menu on a table or catalog:

| Status   | Effect on agents                                                     |
| -------- | -------------------------------------------------------------------- |
| Verified | Preferred when several tables could answer.                          |
| Draft    | The default. Fully usable, with no preference either way.            |
| Excluded | Omitted from default discovery. Used only when the request names it. |

Statuses are set per environment, so a table can be verified in production and draft in staging.

## Excluded data stays reachable

Excluding a table keeps it out of what agents discover on their own. The table is not deleted, and when a request names it, the agent can still query it.

Semantic metrics stay available even when they are built on an excluded table.

## Catalog level

An [Altertable catalog](/docs/lakehouse/catalogs.md) or [external catalog](/docs/lakehouse/external-catalogs.md) has its own endorsement status. Tables discovered later inherit it. Setting a catalog's status overwrites the status of its existing tables, so review table statuses before you change a catalog that mixes them.

Excluded catalogs are left out of the catalog lists agents see. They stay usable by name.

## Endorsement is not a permission

Endorsement steers agents. It does not control who can read data. A user or service account with access to a catalog can still query an excluded table. To restrict access, assign [catalog roles](/docs/administration/access-control.md).

## Learn more

- **[Catalogs](/docs/lakehouse/catalogs.md)**: Create hosted catalogs
- **[Connect existing data](/docs/lakehouse/external-catalogs.md)**: Connect external catalogs
- **[Access control](/docs/administration/access-control.md)**: Restrict who can read data