Group membership can arrive late at a search system even after the identity source changes. Measure and design for that delay instead of describing copied group metadata as current permission by default.
Membership freshness is part of authorisation
A group-membership delay occurs between the authoritative change and the point where dependent components enforce it. Connectors, identity tokens, indexes, caches, and ongoing tasks can each have different update paths.
For a proposed design, record the trusted source, relevant version or observation time, supported propagation behaviour, and safe fallback when freshness is unknown. Distinguish grant delay from revocation delay because their consequences differ.
Do not let the model infer membership from an employee’s message or retrieved document. A claim that someone moved teams is content until the trusted identity and policy systems establish the relationship.
Trace a fictional delayed removal
An employee leaves a restricted project at 11:00. The identity service updates immediately, but a search connector refreshes its copied group list later. The architecture must define whether new requests perform a live check, use a bounded cached policy, or deny while current scope cannot be established.
The test should measure the actual affected paths and report the supported bound. A timer in one component does not prove every answer cache and citation resolver updates at the same speed.
| Delay condition | Verification question |
|---|---|
| Grant not propagated | Is the temporary denial visible and recoverable? |
| Revocation not propagated | What prevents stale protected access? |
| Identity source unavailable | Which safe policy applies? |
| Token retains old groups | How is current authority established? |
| Cache outlives membership | Does reuse revalidate required scope? |
Use simulated membership versions and controlled connector delays. Inspect candidate context and final resource delivery across the timeline.
Make uncertainty operationally visible
Operators need to distinguish a stale membership copy from an ordinary permission denial. Record safe category and freshness metadata without exposing sensitive group names broadly. Provide an accountable path for urgent access correction.
Live checks improve freshness but add latency and dependency. Cached checks can improve availability but require explicit invalidation and exposure limits. Choose from actual risk and infrastructure capability, then validate rather than assume the tradeoff.
This design is proposed. The voice integration case study describes related backend work without claiming enterprise membership guarantees. Pair it with team-change tests.
Membership delay FAQ
Does a successful identity update prove search updated?
No. Verify each dependent enforcement and cache path.
Should grants and revocations share one failure policy?
Assess their different consequences and define the actual supported behaviour explicitly.
What should users hear during a delay?
Provide a safe accurate access-status explanation and approved support path without revealing restricted resource details.