A stale authorization cache is not a current permission

A common shortcut: cache “user X can edit document Y” for a few minutes to save policy round-trips.

That cache is a performance hint, not the policy itself.

If you revoke edit, or move the document to another tenant, a warm cache can still return allow until the TTL expires. For sensitive actions, either use short TTLs with explicit invalidation on revoke or role change, or re-check authorization on every write.

Caching speeds reads. It does not replace authorization.