{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/notifications.manage-preferences/",
    "json": "https://www.anchorterminal.com/niches/notifications.manage-preferences/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/notifications.manage-preferences/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/notifications.manage-preferences/index.min.md"
  },
  "markdown": "Two or three companies' docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 3 | 2 | 5 | 11 | 4 |\n\n## What counts as done\n\nPreferences per channel and per workflow are read and written through the API; after an opt-out on one channel the next trigger skips only that channel, and a workflow marked critical still arrives on every channel.\n\nHow agents ask for it: turn off email for this user but keep push; mute notifications overnight; make security alerts always arrive\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **Courier (trycourier.com, Inc.)**: User Preferences API reads and writes each topic's status and custom_routing channels (email, inbox, push, sms and more); a topic with default REQUIRED cannot be opted out, and writes that try are rejected.\n- **Knock (Knock Labs, Inc.)**: PreferenceSet with channel_types, channels, categories and workflows is read and written by API, with bulk set; workflow override_preferences, which sends despite opt-outs, is a field in the management API.\n- **SuprSend (SuprStack Inc)**: User preference APIs read and update channel and category opt-ins, with bulk update for 100 users; channel preferences are checked at each delivery node, and root categories such as System have no preferences applied.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **MagicBell (MagicBell, Inc.)**: GET and PUT /channels/user_preferences set channels per category, but with a User JWT for that user, and the OpenAPI has no critical or bypass flag for must-arrive messages.\n- **Novu (Noti-Fire Apps Ltd.)**: Subscriber preferences per channel and workflow are read and updated by API, and critical: true bypasses opt-outs, digests and delays. acc-16 reports context preferences not applied when the workflow ran.\n\n- not this job: Amazon SNS (Amazon Web Services, Inc.): No per-user preference store by channel or workflow; only SMS opt-out handling.\n- not this job: Expo Push Notifications (650 Industries, Inc.): No preference store; the service sends to whatever token it is given.\n- not this job: Firebase Cloud Messaging (Google LLC): No preference store; topics are the only grouping.\n- not this job: ntfy (ntfy LLC): No per-user or per-channel preference store; subscribers choose topics in their own app.\n- not this job: OneSignal (OneSignal, Inc.): A channel opt-out is a subscription enabled or disabled by API, but there are no per-workflow preferences or a critical flag that overrides opt-outs.\n- not this job: Pingram (Pingram): The API reference lists no preference endpoints, only removing a user's suppression on one channel; no critical override was found.\n- not this job: Pushover (Pushover, LLC): No preference API; quiet hours are set by the recipient in the app.\n\n## What stops agents finishing\n\n- preferences editable only in a hosted UI component\n- critical bypass set only in the dashboard\n\n## Around it\n\nBefore: notifications.send-user-event. After: notifications.check-delivery.\n\n## Where this comes from\n\nWeight 11 of 100 in Notifications: 4 Novu accounts (acc-16 to acc-19) on context preferences, critical workflows and do-not-disturb\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/notifications.manage-preferences.json, or the MCP tool get_use_case with id notifications.manage-preferences. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Respect and change what a user opted out of",
        "url": ""
      }
    ],
    "description": "Respect and change what a user opted out of: 3 companies fully do it, 2 with a limit, 5 carry the tag. Every listing in Notifications with the reason and a source.",
    "facts": null,
    "h1": "Respect and change what a user opted out of",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/notifications.manage-preferences/",
    "published": "",
    "section": "agents",
    "title": "Respect and change what a user opted out of | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/notifications.manage-preferences/"
  },
  "tokens": {
    "markdown": 1100,
    "slim": 280
  },
  "version": 1
}
