I am guessing there is an answer already for this but I can’t figure out the right search. I saw an example video where an API end point posts and gets files with a username. They build out Keto to protect access to files based on the username which makes sense. Assuming I might want to query ‘all files for user’, I am assuming the username should also be stored in the db with each file? My follow up question would be, if the username on the db row changes there would be a mismatch between the permissions and the data itself right? I would always need to make sure to edit the Keto rule and the db row when updating?

I wouldn’t literally use a dynamic identifier for a user, I’d use a stable unique identifier for the user. But I’m just familiar with using keto directly, I don’t know what it’s like combined with other ory products.