Enable mobile notifications deliberately

Enable mobile push for the intended account and physical device, align Dosya and OS settings, and test delivery without changing unrelated channels.

Last reviewed

Mobile notifications require two independent choices: the Dosya Push notifications channel for the account and notification permission from iOS or Android for this installed app.

Mobile notification setup from account channel through operating-system permission and a controlled delivery test.
Push succeeds only when the account preference, device registration, and OS alert policy agree. Open full-size screenshot.

Steps

  1. In Settings, verify the account email, then choose Notifications under Preferences.
  2. Wait for Notification settings to load. Under Delivery, note the current warning: With In-app off, no notifications are delivered at all - email and push included. The server actually evaluates Email and Push independently; this switch hides inbox rows and disables only the in-app leg.
  3. Turn on Push notifications. Dosya saves the account channel first, then requests OS permission and registers this physical device’s Expo token to the current account.
  4. On the system prompt, allow notifications. Configure banner, sound, lock-screen, or focus behavior in the OS settings; Dosya cannot override those choices.
  5. Leave only the event groups you want under What you hear about. Use a harmless event from another test member when available, then watch the bell and the device alert.

The setting is not plan- or workspace-role-gated. It is account-wide, while a notification’s linked file or team page still enforces workspace membership. Simulators cannot receive push and return Push needs a physical device. A build without its EAS project identity returns Push isn’t configured for this build (no EAS project id).

Dosya mobile availability reference for device-level push permission and registration.
A supported physical installation is required for remote mobile push. Open full-size screenshot.

When Dosya is foregrounded, server push asks the OS to show a banner and notification-list entry with sound, without setting an app badge. Android uses the Notifications channel at high importance. System focus modes, per-app sound settings, battery controls, or a denied OS permission can still suppress presentation.

Expected result

The Push switch remains enabled after reloading settings, the physical device is registered to the current account, and an eligible event can appear as both an inbox row and an OS notification.

Troubleshooting

The app says “Enable notifications for dosya.dev in Settings.” The account preference may already have saved, but OS permission was denied. Open device Settings, allow Dosya notifications, return to the app, and toggle Push notifications off and on to register again.

No prompt appears. The prompt is per installation. If the OS no longer permits asking, change permission in device Settings. Automatic sign-in registration uses a prompt-once rule and will not repeatedly interrupt you.

Another account receives this phone’s push. Signing in re-points an existing token to the current account; explicit sign-out unregisters best-effort before clearing tokens. Sign out, reconnect, and verify the account card if routing seems stale.

Was this helpful?

Loading helpfulness results…

Voting saves a necessary ballot cookie for up to 180 days so you can change your answer.

Questions and replies

Ask about the steps in this guide. Questions are reviewed before publication.

Keep account details, credentials and private files out of public questions. Use private support for those.

Loading questions…

    Sign in to your Dosya account to ask a question.

    Check the outcome before you retry

    Use these shared checks when a task needs a second look.