Notifications and preferences

Notification inbox

Reader and Creator notifications belong to separate app inboxes. Each inbox lists the newest notifications first. The Android Reader, Android Creator and iOS Reader inboxes show the total unread count, including unread items beyond the first page. The reader website and the iOS Creator inbox do not display a number; they offer Mark all read whenever unread notifications exist.

Performer statement notifications appear in Creator. On the Creator website they open Performer rights & pay, which you can also reach from the Tools menu without opening a Story. The Android Creator app opens Performer rights & compensation, listed under Account in its navigation drawer, and the iOS Creator app opens the statement itself.

In the Android and iOS apps, opening a notification requests that it be marked read and opens its destination. If the read request fails, the destination can still open while the row remains unread. Read rows can still be opened. In the reader website, use the check button on an unread row; following the row's link by itself does not mark it read. Mark all read marks every unread notification in the current app's inbox, not only the visible page. Read actions change read state only—they do not remove notification history or change email and push preferences.

In the Android Reader inbox, a failure to load more notifications leaves the loaded rows and your reading position available. The error at the end of the list offers Retry for that same page.

Email and push settings

Notification settings let you turn email and push delivery on or off for the reader app or Creator app. The setting is app-specific, so changing Creator delivery does not silently change reader delivery. Follow the save or confirmation behavior shown by the current settings screen; a failed save is not a confirmed preference change.

Email and push switches control those external channels only. They do not hide in-app rows, so an inbox notification can still be available when email or push is off. Turning a switch off also cannot recall a message that a provider or device already delivered.

The account push switch and the phone's notification permission are separate. Push also requires an active registration for that specific app on the device. Where the app shows notification readiness or a self-test, use it to distinguish an account setting, device registration, phone permission, and delivery-provider problem without exposing the device token.

A notification is absent or delayed

First confirm you are signed into the expected account and checking the correct app inbox. Then check the email or push preference for that same app.

For push, also confirm the phone allows notifications and reopen the app so its current device registration can be refreshed. For email, confirm the expected address is present on the account and check the receiving mailbox's filtering. If the in-app row exists but push or email did not arrive, include the notification title, reader-or-Creator app, and approximate time when contacting support. Never paste a device token, access token, or sign-in code.

Language preference

Localized inbox and API text uses the account's stored language preference when one is set, followed by the language requested by the current app or browser, then English. Notification email uses the stored account language and falls back to English. Push is localized for each registered device's current app language, so two devices on the same account can correctly receive the same event in different languages. User-written content, such as a message preview, is not translated.

A saved language change applies to later localized responses. The website reloads after a successful change; Android saves the account preference before applying and recreating the app language. If already-open content remains in the earlier language, close and reopen that screen.