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

<AgentInstructions>

## Submitting Feedback

If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:

POST https://docs.omni.co/feedback

```json
{
  "path": "/connect-data/schema-restriction",
  "feedback": "Description of the issue"
}
```

Only submit feedback when you have something specific and actionable to report.

</AgentInstructions>

# Restricting connection schemas

> Limit which schemas are included in your Omni model to improve performance and control model scope.

<Warning>
  This guide applies to the **Included schemas** field in the connection settings page. For the modeling parameter, which restricts the schemas that are accessible in workbooks, refer to the [`included_schemas`](/modeling/models/included-schemas) reference.
</Warning>

When a database connection includes many schemas, your Omni model can become larger than necessary. Restricting which schemas are included helps improve performance, reduces clutter, and ensures only relevant data is modeled.

## Requirements

**Connection Admin** permissions are required to modify connection settings.

## Defining included schemas

You can control which schemas Omni pulls into your model using the **Include schemas** field in the connection settings. Only the listed schemas will be included when the model is built.

If this field is left blank, Omni will include all available schemas in the accessible databases for that connection.

When finished modifying the connection settings, trigger a [schema refresh](/modeling/develop/schema-refreshes) to apply the changes to the model.

## Example configuration

The **Include schemas** field accepts a comma-separated list of schema names, and also supports wildcard syntax for partial matches.

<Note>
  The values in **Included schemas** are case-sensitive, meaning they must exactly match the name of the schema in the database.
</Note>

```yaml title="Include only the blob_sales schema" theme={null}
blob_sales
```

```yaml title="Include only the blob_sales & blob_marketing schemas" theme={null}
blob_sales, blob_marketing
```

```yaml title="Include only schemas starting with blob_" theme={null}
blob_*
```

## Related

* [Offloading schemas](/connect-data/offloading-schemas)
* [Incorporating database changes with schema refreshes](/modeling/develop/schema-refreshes)