Caching

hasPermissionThroughConnection() — and everything built on it: the any/all variants, permissions()->has() / hasAny() / hasAll() and the Gate hook — memoises the resolved connection per connector–connectable pair, so a page that checks access many times queries once:

$user->hasPermissionThroughConnection($team, 'edit');               // queries once, then memoised
$user->hasPermissionThroughConnection($team, 'view');               // served from the cache
$user->hasPermissionThroughConnection($team, 'edit', force: true);  // re-query and refresh the entry

Connections::between($user, $team)->permissions()->revoke('edit');  // writes invalidate the pair
$user->hasPermissionThroughConnection($team, 'edit');               // false — no force needed

• The cache stores the Connection row, not the answer, so status and expiry are evaluated at check time.
• Every write through the package — facade, trait, actions, bulk verbs and sync — invalidates the affected pair; connections:prune and Connections::prune() drop the whole cache once they remove rows.
• isConnectedTo() and the other connected-to checks always query the database.
• Set cache.enabled to false to re-query on every check.

Cache lifetime

The cache is a scoped container instance, dropped at the start of every request and queued job — Octane and queue:work included — so a cached permission never outlives one. Within a single request or job it can still miss changes made outside the package’s write path, such as another process or a direct Eloquent update to a Connection. Pass force: true where freshness matters, disable the cache, or flush it mid-request through the facade:

use RoundlyConsulting\Connections\Facades\Connections;

Connections::flushCache();   // forget every memoised connection