Enable browser push notifications
Grant browser permission, register a secure web-push subscription, align Dosya channel settings, and diagnose denied or unsupported states safely.
Last reviewed
Browser push needs two independent approvals: the browser must grant notification permission and Dosya must register that browser to the signed-in account. Delivery then requires the Browser push master switch, an eligible event group, and a catalog entry that supports push.

Requirements
Use the signed-in web app in a browser that exposes both a service worker and PushManager. Service workers require a secure context in normal browser operation. The account plan and workspace role do not affect registration.
If the browser has already blocked notifications for Dosya, its permission prompt may not reappear. Change the site permission in browser settings first, then return to the web app.
Steps
- Open Profile > Notifications in the browser and account that should receive alerts.
- Under Delivery channels, turn on Browser push. This switch controls delivery but does not itself create a browser subscription.
- Select Enable browser notifications.
- In the browser prompt, choose Allow.
- Wait for Dosya to obtain its application key, create a user-visible push subscription, and register the endpoint to your account.
- Confirm the success toast Browser notifications enabled.
- Keep the required event group enabled and trigger one harmless event whose catalog entry supports push.
Registration stores the endpoint, encryption keys, and up to the first 80 characters of the browser user-agent as the device name. Re-registering the same endpoint for the same account refreshes its keys and clears a prior revocation. An endpoint already owned by a different account is rejected rather than reassigned.

Permission and delivery failures
- Permission denied with “Allow notifications in your browser settings” means the permission result was not
granted. - Not supported with “This browser can’t receive web push” means service-worker or PushManager support is absent.
- A server without a configured public push key returns Push not configured. Registration can also fail for missing fields, an unsupported endpoint host, or an endpoint tied to another account.
Dosya submits web-push messages with a 60-second time-to-live. Delivery is best effort; closing the app is supported, but a push service or offline device can miss that short window. A 404 or 410 response from a push provider causes the stored subscription to be revoked automatically, after which enabling again creates or refreshes the live registration.
Selecting an operating-system notification closes it, focuses the first existing Dosya window and navigates to the event path, or opens a new window. When no path is supplied, it goes to /notifications.
Turning off Browser push stops eligible delivery without revoking browser permission or unsubscribing the endpoint. To remove site permission, use the browser’s settings; this action is reversible by granting it again.
Expected result
The browser grants notification access, Dosya confirms registration, and a push-eligible controlled event produces an operating-system notification for this account. Selecting it opens the stored destination or the notification inbox fallback.
Related guides
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.