When set to true, permission checks are performed without caching, meaning that each permission evaluation is processed from scratch. This ensures permissions are always current but may impact performance.

When set to false, permission results are cached for performance, so repeated permission checks for the same user/resource can be served from the cache. This can improves performance in systems with many permission checks, but may cause a slight delay in reflecting permission changes.

In most systems, permission caching should remain enabled for performance reasons, but it can be temporarily disabled when immediate permission updates are critical or when diagnosing permission-related issues.