> ## 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.

# tags - Dimensions

> Apply tags to dimensions for searchable metadata in workbooks and use tag syntax to curate topic fields and drill field lists.

Tags can be referenced or searched in the workbook's field browser within `fields` or `drill_fields` with the syntax `tag:tag_name`.

## Syntax

```yaml theme={null}
<dimension_name>:
  tags: [<tag_1>, <tag_2>, ...]
```

## Properties

<ParamField path="dimension_name" type="object">
  The name of the dimension. Dimension names must:

  * Be unique within the view
  * Start with a letter
  * Contain only alphanumeric characters and underscores

  <Expandable title="dimension_name properties" defaultOpen="true">
    <ParamField path="tags" type="string[]">
      An unquoted list using `[]` and a comma-delimited list of tag values.

      If using [Databricks Unity Catalog](/connect-data/databricks-unity-catalog-integration), schema refreshes automatically populate this parameter from the column's Unity Catalog `COLUMN_TAGS`. A tag with a value renders as `name: value`, and a tag without a value renders as a bare `name`. This doesn't apply to legacy `hive_metastore` catalogs, which don't have Unity Catalog tag data. If you edit `tags` in the shared model, your changes are preserved on later refreshes.
    </ParamField>
  </Expandable>
</ParamField>

## Examples

```yaml title="PII tags" theme={null}
full_name:
  sql: CONCAT(${first_name}, ' ' ${last_name})
  tags: [pii, secure]
```

```yaml title="Finance tags" theme={null}
profit:
  sql: ${sales} - ${cost}
  tags: [finance, secure]
```

```yaml Databricks Unity Catalog tag with a value theme={null}
full_name:
  tags: [ "pii: A"]
```

```yaml Databricks Unity Catalog tag without a value theme={null}
full_name:
  tags: [ pii ]
```