Say which kinds of notification will be sent

What it is

When notification permission is requested, people need to see which types will arrive: orders and shipping, account security, messages from people, marketing—not "turn on notifications so you never miss an update." The type list is material for the authorization decision. It is not the title of each later push, and not a cap on how many of each type per day. This entry stops at disclosure at the moment of the ask. How urgency is graded, how copy is written, and how alerts are bundled belong to notification patterns.

Why it happens

The system dialog only says "Allow notifications"; the scope is the whole channel. People estimate interruption by content type: a security alert can be acceptable, a promotion cannot. Without types at request time, Allow is a master valve over unknown classes, and the only later regret is shutting the whole channel. Listing types also makes a checkable promise: if a class that was not on the list appears after the grant, people can name the overreach instead of wondering whether they once agreed to "any update." When disclosure fails, refusal often targets the worst imagined class (ads) and takes security with it.

Where it stops holding

If types are not yet knowable at ask time (no interests chosen, no orders yet), write "for now, only account security; other types will be asked before they start"—do not invent a catalogue of possible future sends. When the system purpose string cannot hold a list, put the list on the pre-prompt and align the dialog's short sentence with the first item. A legally complete policy does not replace the type list; the policy can be linked out, the list has to be present.

Applying it

• On the notification-permission pre-prompt, list the types that will be enabled, each with one understandable example ("back in stock," "new device signed in"), and mark which types will not be sent now.
• Map the list one-to-one onto notification categories or channels the app will actually register. Do not name a class that the code will not send.
• If the system dialog can hold only one sentence, name the broadest or most sensitive type there; leave the full list on the pre-prompt.
• Verify by showing uninvolved people the request UI (including the pre-prompt) and, before they tap Allow, asking them to write which types they think will arrive. Missing marketing, or reading marketing as a system alert, means disclosure failed. Then sample the types actually sent in the first week after launch against the list.

Related

• Within the group: H4.05.1 Ask for notification permission after the product has delivered value · H4.05.3 Category opt-in beats a blanket grant
• Adjacent: H5.01 Urgency Grading · H5.09 Category Subscriptions · O2.02 Explaining Data Use
• Search terms: notification category · permission-time disclosure · push types