Does ShotGrid permission caching differ between local and production environments?

ShotGrid utilizes role-based access control (RBAC) to manage user permissions based on group memberships. In local development environments, configurations often rely on in-memory caches or embedded databases, whereas production deployments typically utilize persistent caching layers and external database clusters.

There is uncertainty regarding how these divergent caching mechanisms handle permission state persistence, particularly when group memberships are updated after a user session has already been established. If production environments enforce stricter session-based permission snapshots compared to local setups, it could lead to scenarios where access changes do not propagate in real-time.

• Does ShotGrid's permission evaluation logic vary when moving from a local in-memory cache to a production persistent cache?
• What is the expected behavior for group membership updates regarding session refresh requirements in a production environment?