> Not sure I follow. If the schema is updated, it will be used by all requests after the caches become invalid, which is ~5s as stated above I just wanted to check in regards to this article: https://authzed.com/blog/online-schema-migrations/ Since we need to backfill the data, what would happen if we forgot a handful of customers, for example. I assume they would be checked against the old schema before that which might not be great. Being able to detect that some customers are not using the latest could be useful (although I assume this might be beyond the scope of SpiceDB itself) > Do you mean when you want to change it? Yes. To give you more context, we do what we call "antisocial screening". If a customer might be a criminal, we put ACLs on him. The customer is then checked and if he's a criminal, we just leave the ACLs as-is. Otherwise, we just remove ACLs so that he can use the application again.