Each staff member controls the alerts available to their role, including in-app and browser delivery where supported. Browser push requires permission in that browser and a registered device subscription.
Owners and admins control organization-level delivery behavior, including how upload activity is summarized. Available modes may favor a digest, completion-only notification, or immediate per-file updates.
Email is the current client delivery channel and remains enabled for request links, reminders, and staff replies. NeuDocs does not currently send native WhatsApp messages.Firms with their own WhatsApp Business setup and phone records can relay signed client-facing webhook events through Zapier, Make, n8n, or a custom service. NeuDocs does not store client phone numbers; the relay must look them up in your CRM. Register interest in native WhatsApp under Settings → Notifications → Delivery channels → WhatsApp.
Notification processing is asynchronous. A client upload can complete before an email, push notification, or webhook arrives. The in-app record remains the canonical workspace notification. Webhook delivery is best-effort and is not retried.
Notification titles and bodies avoid raw document text and secrets. Still treat device notifications as potentially visible on a lock screen and disable push on shared devices. Treat every client portal URL as a credential and do not place it in logs or public channels.
