Yes, Elementary already uses the model owner as a fallback for test alerts when no specific test owner is defined. This is the default behavior. According to the [configuration documentation](https://docs.elementary-data.com/oss/guides/alerts/alerts-configuration#alert-properties-in-yml-files), Elementary prioritizes configuration in the following order for tests: 1. Test properties 2. Tests path configuration under

tests

key in

dbt_project.yml

3. Parent model configuration This means that if you don't define an owner at the test level, Elementary will automatically use the owner from the parent model that the test is associated with. This is confirmed in several community discussions where users were advised that [if they configure an owner for the model the test is referencing, it will be picked up from there](https://slack.com/archives/C02CTC89LAX/p1675867987431539). However, there's an important note: Currently, when you define both a model owner and a test owner, both owners are tagged in test alerts because [owner is an aggregated field](https://slack.com/archives/C02CTC89LAX/p1688392078242689). The Elementary team has discussed potentially changing this behavior so that the model owner would automatically be considered as a subscriber on tests instead, maintaining a single owner per alert while keeping the model owner aware of test failures.