Where notifications appear
| Surface | Shows | Good for |
|---|---|---|
| Rail counts | Unread per module | Knowing which module wants you without leaving the one you are in. |
| Home activity feed | Recent events across the suite | Catching up after a day away. |
| Module inbox | That module's own queue | Working through a specific backlog. |
| Things that must reach you | Approvals, signature requests, invitations. |
The rail count is the one people rely on most, because it works from inside another module. Approvals waiting in Sign show on the Sign icon while you are in Accounting.
Changing what you get
Settings → Notifications is per person, not per organisation — your preferences do not change anybody else's. Categories are grouped by what the notification is *about* rather than by which module sent it, because "somebody needs my signature" is the same interruption whether it came from Sign or from the portal.
Notifications
Email delivery
All product email — invitations, magic links, approvals, signature requests — goes through one transactional provider on authenticated domains. Two things about that are worth knowing, because both look like product faults and are not.
Transactional providers apply suppression account-wide. If somebody clicks unsubscribe on any message from us, later mail to that address is accepted by the provider and silently dropped — including their magic link. The symptom is a person who "never gets the email" while our logs show it sent successfully. If that happens, mail [email protected] with the address and we will clear the suppression.
Security gateways fetch every URL in an inbound message. A magic link is single-use, so the scan spends it and the real click fails. Use a password or Google on domains where this happens. See Create your account.
What deliberately does not notify
- Routine agent activity. An agent classifying a transaction does not interrupt anybody. Its output is reviewed in the module, in a batch.
- Spend. AI usage and metered call time are visible but do not alert. See Operate.
- Audit events. Nothing pages you when a role changes. The log is read, not pushed.
- Another person's work. Activity feeds show what happened; they do not notify you about it unless you are involved.
What this does not do
There is no mobile application, so no push notifications.
Notifications reach in-product surfaces and email only.
An administrator cannot set notification defaults for everybody.
Email sends when the event happens.
Questions
Can I get a daily digest instead of individual emails?
Yes, for the categories that support it. Turn the individual ones off and the digest on.
Why did I get an email I did not ask for?
Invitations, signature requests and password resets are transactional and always send.
Can I forward notifications to a shared mailbox?
Not from settings. A mail rule on your side is the usual answer.