Notifications (Push & Email)
Signed-in users configure delivery at Settings → Notifications, /settings?tab=notifications.
Date: 2026-09-30 Purpose and access Signed-in users configure delivery at Settings → Notifications, /settings?tab=notifications. The settings section has no paid-tier gate, but events depend on the features/content available to the account. Web browser push and native mobile push are separate channels. Workflow Review event preferences such as watchlist reports, featured reports and Oscar completion where displayed. Toggle Email for email delivery and Mobile for account-level native push delivery. In a supported browser, enable Browser notifications. Accept the browser's permission prompt to subscribe this browser/profile. To disable browser delivery, turn that control off; it unsubscribes this browser only. Changing Mobile does not disable Browser. Check the saved message and resulting toggle state. Open a received notification to follow its available destination. Results, limits and states Saving preferences can show busy/error feedback; a failed save must not be treated as confirmation. A browser without a subscription begins off. Denied permission leaves Browser off with guidance: change the site's permission in browser settings, then reload. Unsupported browsers/webviews cannot be fixed by repeatedly toggling; iOS web push requires the supported home-screen setup. Native delivery also requires a registered device and OS permission. After reinstalling, open the app while signed in to re-register. This documents configuration, not guaranteed delivery timing or full Oscar Mobile parity. No notification event means there may simply be no new eligible content; the preference screen is not an inbox. Never assume a missing push means a report was not generated. Scheduled queries in this tab Settings → Notifications → Scheduled queries is a card in /settings?tab=notifications, not a separate Settings tab or the Oscar Assistant tab. Review the saved question, cadence, notification condition, status and run/notification counts. Use the switch to pause/resume an existing schedule. Delete sends the removal directly; the card does not provide a second confirmation dialog. Expand recent runs to see up to five results, timestamps, success/error/running status and whether the condition matched. An answer preview is not a newly published report. The card manages existing schedules, not a full creation form. Empty schedules and no-runs states are distinct. Loading and mutation errors must not be treated as completion; the run list lacks a dedicated loading/error presentation and can initially look empty. Scheduling eligibility and execution remain server-controlled; a schedule does not guarantee delivery or bypass interactive approvals.