We have tables that are modified outside of the application (etl loads) that need to also be included in the audit of changes. We can handle the app and etl changes using triggers, but if we follow the ENVERS table structure would it be possible to additional Criteria querying apis without having to set the entity as @Audited? Basically setting the table as Audited by the db like you can specify at a column level whether it's value is generated on insert/update.