# Respect and change what a user opted out of

> 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.

- Canonical: https://www.anchorterminal.com/niches/notifications.manage-preferences/
- Markdown: https://www.anchorterminal.com/niches/notifications.manage-preferences/index.md (~1,100 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.manage-preferences/index.min.md (~280 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.manage-preferences/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Two or three companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 3 | 2 | 5 | 11 | 4 |

## What counts as done

Preferences 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.

How agents ask for it: turn off email for this user but keep push; mute notifications overnight; make security alerts always arrive

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **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.
- **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.
- **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.

## Does the job, with a limit

It 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.

- **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.
- **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.

- not this job: Amazon SNS (Amazon Web Services, Inc.): No per-user preference store by channel or workflow; only SMS opt-out handling.
- not this job: Expo Push Notifications (650 Industries, Inc.): No preference store; the service sends to whatever token it is given.
- not this job: Firebase Cloud Messaging (Google LLC): No preference store; topics are the only grouping.
- not this job: ntfy (ntfy LLC): No per-user or per-channel preference store; subscribers choose topics in their own app.
- 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.
- 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.
- not this job: Pushover (Pushover, LLC): No preference API; quiet hours are set by the recipient in the app.

## What stops agents finishing

- preferences editable only in a hosted UI component
- critical bypass set only in the dashboard

## Around it

Before: notifications.send-user-event. After: notifications.check-delivery.

## Where this comes from

Weight 11 of 100 in Notifications: 4 Novu accounts (acc-16 to acc-19) on context preferences, critical workflows and do-not-disturb

As 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.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
