{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Coach client access after reassignment",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/coach-client-access-permissions",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Map roles and assignment relationships explicitly",
    "Recheck access on every protected operation",
    "Test old tabs direct requests and reassignment reversals"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "Former coach sends a direct record request",
      "expectedBehavior": "Current assignment policy is enforced",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "Owner views the reassigned client",
      "expectedBehavior": "Administrative access follows explicit role rules",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "Cached data survives reassignment",
      "expectedBehavior": "The UI clears or labels it according to policy",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "Instantly disconnecting every open session may add complexity. The essential boundary is that new protected requests use current authorization; cache invalidation and real-time updates improve the experience around that rule."
}