{
  "status": "Illustrative acceptance plan, not an executable test suite or observed production result",
  "topic": "Health permission revocation UX",
  "date": "2026-11-04",
  "sourceArticle": "https://aptixlabs.com/insights/health-app-permission-revoked",
  "setup": [
    "Use synthetic accounts and records",
    "Record the environment and implementation version",
    "Agree the expected product contract before testing"
  ],
  "reviewSequence": [
    "Map each permission to the affected product behavior",
    "Separate retained history from future synchronization",
    "Test partial revocation and explicit reconnect"
  ],
  "cases": [
    {
      "id": "1",
      "condition": "One metric permission is unavailable",
      "expectedBehavior": "Other permitted workflows still function",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "2",
      "condition": "Cached permission state is stale",
      "expectedBehavior": "Revalidate before access",
      "observedBehavior": null,
      "status": "not_run"
    },
    {
      "id": "3",
      "condition": "User requests deletion",
      "expectedBehavior": "Follow the separate documented data-removal process",
      "observedBehavior": null,
      "status": "not_run"
    }
  ],
  "tradeoff": "A single all-or-nothing permission screen is easier to build but can unnecessarily block unrelated features. Granular states require more testing and clearer copy."
}