> ## 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": "/modeling/models/default-topic-access-filters",
  "feedback": "Description of the issue"
}
```

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

</AgentInstructions>

# default_topic_access_filters

> Defines default access filters for topics in the model.

Defines a list of default access filters for topics in the model. Access filters limit row-level access to data based on user attributes.

## Syntax

```yaml theme={null}
default_topic_access_filters:
  - field: <view>.<field>
    user_attribute: <user_attribute_reference>
  - field: <view>.<field>
    user_attribute: <user_attribute_reference>
```

<ParamField path="field" type="string" required>
  The name of a field, specified using `<view>.<field>` convention, to match to the `user_attribute`.
</ParamField>

<ParamField path="user_attribute" type="string" required>
  A user attribute reference. Records with `field` values that match the user's attribute value will be visible to the user.

  For example, if a user has a `customer` value of `blobsrus` and the `products.brand` field in a record has a `blobsrus` value, the user will have access to the record.
</ParamField>

## Examples

```yaml title="Match brand field value to customer user attribute value" theme={null}
default_topic_access_filters:
  - field: products.brand
    user_attribute: customer
```

## Troubleshooting

If an access filter can't be mapped to a topic, an error will surface in the model IDE. Add a blank [`access_filters`](/modeling/topics/parameters/access-filters) parameter to the topic to resolve the issue:

```yaml title="Topic file" theme={null}
access_filters: []
```