OYYO AI NotzUp: Capture All · guide
Notifications
Review in-app notifications, mobile permissions and delivery states without assuming a push was delivered.
Before you begin
- A signed-in account; for mobile push, a registered supported installation and explicit OS permission.
- An event/channel that is enabled and configured; not every catalog event is necessarily available.
Step by step
Open the notification center
Review notifications for the current account and follow only intended event links.
Manage preferences
Choose supported notification preferences and grant mobile OS permission only if you want push alerts. Device-level denial can prevent push even when an in-app event exists.
Mark or remove notifications
Mark individual items or all read. Use archive/delete actions deliberately and confirm bulk deletion when requested.
Check the actual state
An in-app notification is not proof that email or push arrived. Provider acceptance, delivery and read status are different; configuration, permission and network state matter.
Expected result
A reviewed notification center and intentional channel preferences.
Privacy and permissions
Recordings, files, searches, scans, OCR, barcode counts and supported local-AI results do not leave the device by default. Only a deliberate online action—Share, Search online, connector authorization or encrypted backup—transmits the selected data or value. Language-pack downloads do not upload the source text. Mobile dispatch queues notification identifiers and loads authorized content when sending. Do not assume permission to broadcast private notes or include sensitive material in an external notification.
Troubleshooting
No mobile alert
Check OS permission, device registration, connection and channel availability. Open the in-app center; real device delivery is not guaranteed by an event row.
An old item remains unread
Refresh the current account view and use mark-read; bulk actions affect only your authorized notification items.