> For the complete documentation index, see [llms.txt](https://v2.dataos.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v2.dataos.info/references/resources/vulcan/configurations/model-defaults.md).

# Model defaults

Configure model\_defaults in config.yaml: the required dialect, owner enforcement against config.users, identifier normalization strategy, and how they pair with the default gateway.

The `model_defaults` section is required. You must specify a value for the `dialect` key.

All supported `model_defaults` keys are listed in the [configuration reference](https://v2.dataos.info/references/resources/vulcan/configurations.md#model-defaults).

## Basic configuration

Example:

```yaml
users:
  - username: jen
    email: jen@example.com
    type: OWNER

model_defaults:
  dialect: snowflake
  owner: jen
  start: 2022-01-01
```

The default model kind is `VIEW` unless you override it with the `kind` key. See [model kinds](https://v2.dataos.info/references/resources/vulcan/models/data-models/model-kinds.md) for more information.

## Owner enforcement

The `owner` field in `model_defaults` is subject to the following rules at config load time:

* **Default value.** If `model_defaults.owner` is not set, it defaults to the `username` of the first entry in `config.users`.
* **Must be a listed user.** Whether set explicitly or defaulted, the resolved owner must be a `username` present in `config.users`. If it references an unknown username, config load fails.
* **Per-model validation.** Each model's individual `owner` field is also validated against `config.users` at load time. A model that names an owner not listed in `config.users` is rejected with a load error.

{% hint style="warning" %}
`config.users` must contain at least one entry. If the list is empty or the key is omitted, config load fails before `model_defaults.owner` is resolved.
{% endhint %}

Example showing all three levels: project users, a default owner, and a per-model owner override:

```yaml
users:
  - username: jen
    email: jen@example.com
    type: OWNER
  - username: data_team
    email: data-team@example.com
    type: MEMBER

model_defaults:
  dialect: snowflake
  owner: jen          # defaults to "jen" even if omitted, because jen is first in users

# In a model file, you can override the owner, but only with a username from config.users:
# MODEL(
#   name analytics.daily_sales,
#   owner data_team,   -- valid: data_team is listed in config.users
# );
```

## Identifier resolution

When a SQL engine receives a query like `SELECT id FROM "some_table"`, it needs to understand what database objects the identifiers `id` and `"some_table"` correspond to. This is identifier resolution.

Different SQL dialects resolve identifiers differently. Some identifiers are case-sensitive if quoted. Case-insensitive identifiers are usually lowercased or uppercased before the engine looks up the object.

Vulcan analyzes model queries to extract information such as column-level lineage. To do this, it normalizes and quotes all identifiers in queries, respecting each dialect's resolution rules.

The normalization strategy determines whether case-insensitive identifiers are lowercased or uppercased. You can configure this per dialect. To treat all identifiers as case-sensitive in a Databricks project:

{% tabs %}
{% tab title="YAML" %}

```yaml
model_defaults:
  dialect: "databricks,normalization_strategy=case_sensitive"
```

{% endtab %}
{% endtabs %}

Use this when you need to preserve name casing. Vulcan does not normalize identifiers.

See [normalization strategies](https://sqlglot.com/sqlglot/dialects/dialect.html#NormalizationStrategy) for all supported options.

## Model defaults with a gateway

Set `model_defaults` at the top level of `config.yaml`, next to your gateway definition:

```yaml
gateways:
  snowflake:
    connection:
      type: snowflake

default_gateway: snowflake

model_defaults:
  dialect: snowflake
  start: 2025-02-05
```

In the example above, `default_gateway` (line 6) tells Vulcan to connect through the `snowflake` gateway when you don't pass `--gateway`. The top-level `model_defaults` apply to every model in the project, so models are written in the `snowflake` dialect (line 9).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://v2.dataos.info/references/resources/vulcan/configurations/model-defaults.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
