Manage email notifications

Set the Email channel and event groups, learn which notices remain mandatory, and diagnose delivery without exposing file details or secrets.

Last reviewed

Dosya notification email uses the signed-in account address. Delivery is decided by the event’s supported channels, its event-group preference, and the Email master switch. Email is best effort, so the in-app inbox remains the authoritative place to inspect current account activity and access.

Email alert setup from the account address through channel and event eligibility to inbox verification.
Check the account address first, then align the Email channel and the event group before testing delivery. Open full-size screenshot.

What email can send

For a new account with no stored overrides, email delivery defaults on for Security and sign-in, Account, Team and permissions, Billing and storage, File requests, Sync and backup, Support and legal, and System. It defaults off for File activity, Share links, Comments, Imports and transfers, Integrations and API, and Product updates. The event catalog is still a ceiling: enabling a group cannot add email to an event that has no email version.

The settings page saves one switch at a time. There is no send-test button. Explicitly changing a group stores an account override, while the Email row remains a separate master gate.

Some security, account, billing, legal, and service messages are mandatory. Mandatory mail ignores both the group preference and the Email master switch. Its footer says it was sent regardless of notification settings and omits the unsubscribe link. Ordinary notification messages include a settings link back to Dosya when an unsubscribe destination is available.

Steps

  1. Open Profile and verify the account email shown there. If it is wrong, correct the account identity before testing alerts.
  2. Visit Profile > Notifications and turn on Email under Delivery channels.
  3. Enable the group for the event you need. Read any always-on note beside that group.
  4. Trigger a low-risk supported event once. Avoid putting confidential filenames or personal information in a test comment or request.
  5. Check the primary inbox, spam or junk, rules, quarantines, and any forwarding destination for the account address.
  6. Match the subject and action to the event in Dosya. Open the web app directly when the message concerns permissions, billing, or a shared file.
  7. Reload notification settings to make sure the channel and group values persisted.
Profile identity details for confirming the destination address of Dosya account email.
The profile address identifies the mailbox used for catalog-driven account notifications. Open full-size screenshot.

When mail does not arrive

If the Email switch immediately reverts, Dosya shows Couldn’t save and “Your channel preference could not be saved.” Retry after restoring connectivity. If the setting persists but mail is absent, verify that the specific event supports email, its group is enabled, and mailbox filtering did not divert it. A successful in-app entry does not prove the independent email transport succeeded.

Do not forward a sensitive notification as a substitute for sharing through Dosya. The current file, role, link, or billing state can change after a message is sent.

Expected result

The selected Email and event-group controls survive a reload, and a supported controlled event arrives at the account mailbox with content and an action matching the corresponding Dosya activity. Mandatory notices remain deliverable even when optional email is muted.

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.