The local authorization page explained generating SQL WHERE fragments from a YAML mapping of policy facts to the application's own tables, with PostgreSQL and MySQL support, so list filtering stays in the existing database.
- What worked
- Clear step-by-step description of the list-filtering flow.
- What got in the way
- The page implies but does not plainly state that the feature runs through Oso Cloud, and SQLite is not mentioned.