Skip to main content

Notifications

In this article, you will learn how to review notifications, open related records, mark messages as read, and check recipient setup.

Screenshot placeholder

Add screenshots of the notification bell, Notifications list, notification detail links, organization recipients, linked users, and effective recipients.

Before You Start​

Use notifications when an order, upload, standing order, or account action needs attention. Recipient setup is managed from the related customer, farm, or organization record.

Review Notifications​

  1. Select the notification bell.
  2. Review unread messages first.
  3. Open a notification when it points to an order, upload, standing order, or detail page.
  4. Complete the related task.
  5. Mark the message as read.
  6. Use Mark All Read after reviewing the full list.

Check Notification Recipients​

  1. Open Users And Organizations.
  2. Open the customer or farm organization.
  3. Review Notification Emails.
  4. Review linked users with Notify on orders turned on, and with Invoice emails turned on.
  5. Open Effective Recipients to confirm who receives messages.

Effective Recipients lists every address configured on the organization and shows, for each one, whether it receives Orders and whether it receives Invoices. The two columns are answered separately because the two preferences are separate (see below). Farm organizations show only Orders: farms are not billed, so there are no invoice messages to receive.

Deactivated users do not receive email, whatever their notification settings say. Turning an account back on restores its messages; no notification setting has to be re-entered.

A deactivated organization receives no email either, and the same rule applies to every message type: order confirmations, cancellations, updates, and invoices. Its notification emails and its linked users' settings are all kept exactly as they were, so turning the organization back on restores its messages with nothing to re-enter. Effective Recipients says so directly: the addresses stay listed, every delivery column reads as not receiving, and a notice above the list explains that nothing is delivered while the organization is deactivated.

The same notice appears, with its own wording, in two other cases. One is when another organization is linked to the same customer or farm record and receives that record's messages instead. The other is when the organization is linked to no record at all — notifications are addressed through the customer or farm record behind an organization, so one without a record receives nothing. A farm organization starts this way, because creating an organization does not link a farm record to it; link one to begin delivery. In each case the addresses configured here are correct and still unused, which the list would otherwise show as an unexplained blank.

Order And Invoice Preferences​

Notify on orders and Invoice emails are separate choices, and each one is honored on its own:

  • Notify on orders covers order confirmations, cancellations, updates, and notices that a standing order did not generate an order this week.
  • Invoice emails covers issued, reissued, and cancelled invoices.

Turning on one does not turn on the other. A person who wants order messages but not invoice copies leaves Invoice emails off, and still receives every order message.

Turning Invoice emails off stops future invoice copies to that person. When no one at a customer receives invoice emails any more, a later reissue or cancellation of an invoice shows the customer invoice notification on that order as Not Required rather than as a failed delivery. This happens whenever an invoice email to that customer was attempted earlier on the order, whether or not it was delivered. Nothing was owed, so there is nothing to retry.

Troubleshooting​

  • If someone did not receive an order message, check organization email recipients and linked-user notification settings.
  • If a person with Notify on orders turned on still receives nothing, check whether their account is active.
  • If a notification opens an unexpected page, confirm the order number, upload, or organization before making changes.
  • If a retry fails, confirm the recipient email address before retrying again.
  • An order sent to several farms lists each farm's message separately and names the farm on each row, so one farm's delivery problem can be retried without resending to the others.
  • A farm with no email address configured still appears in the list, named and marked as having no recipient. Add the address on the farm record, then retry that row.
  • A farm whose recipients could not be looked up at all also appears in the list as a failed row, with the reason recorded on it. Retrying that row uses the current recipient setup rather than resending the original attempt, so it succeeds once the underlying problem clears — no change to the farm record is needed.
  • If a customer or farm stops receiving messages entirely, check whether their organization is still active in Users And Organizations.
  • Retrying an invoice message reports that the invoice has since been replaced or cancelled when that is the case, and sends nothing. An invoice that has been superseded is no longer the order's current paperwork, so re-sending it would state something untrue about a financial document. Reload the order and act on the newer invoice notification instead.