Skip to content
Evergrowth Documentation

Manage notifications

Notifications tell you when background work finishes, and when something running quietly needs a decision from you, so you do not have to watch a feed. Workflow runs, contact finder runs, exports, imports, contacts that need review, bulk merges or deletes, and a duplicates resync each post a notification when they complete or fail, with a link straight to the result. A run that pauses on credits posts one as well, naming which ceiling stopped it: the workspace running out of credits, your own credit limit, or your team’s. Ownership and CRM-mapping problems post one too: an ownership rule that has no active assignees left, one switched off after repeated failures, somebody dropped from a rotation because their CRM seat was deactivated, and a CRM user mapping that has gone stale. This page shows how to open the list, read it, and clear what you have seen.

There is no role or environment restriction on notifications - any signed-in member of a workspace sees their own.

Steps

Section titled “Steps”
  1. Open the workspace and look at the top of the screen. The bell control is labeled Notifications. A red count badge on it shows how many notifications you have not yet read.
  2. Click Notifications to open the dropdown. It lists your most recent notifications. Use View all at the top of the dropdown to open the full Notifications page.
  3. You can also reach the full page from the account menu at the bottom of the left sidebar (your avatar and email): open it and choose Notifications.
  4. On the Notifications page, read the list top to bottom (newest first). Each entry shows a title, a short message, how long ago it arrived, and a colored status label: Info, Success, Warning, or Error. Unread entries are highlighted with a colored border.
  5. Click any entry to jump to what it is about. A finished, failed, or credit-paused workflow opens it in the Agent tasks feed; a finder result opens the contacts it produced; a contact flagged for review opens the pending review screen; an export or import opens its history, as does a bulk merge or delete; a finished duplicates resync opens the duplicates list for that record type, while a failed one opens Choose what counts as a duplicate so you can start it again; an ownership-rule warning opens the Ownership rules page.
  6. To clear a single entry, click Mark as read on that entry. The button only appears while the entry is still unread.
  7. To clear everything at once, tick a checkbox to bring up the actions bar, then click Mark all as read. This marks every notification as read, not just the ones you ticked. Closing the bell dropdown also marks everything as read.

When you have no notifications, the page shows No notification yet.

The pop-up card when a run finishes

Section titled “The pop-up card when a run finishes”

You do not have to be watching the bell. When a workflow run finishes, fails, or stops because it ran out of credits, a card slides in at the corner of the screen with the finished task on it: what the run was, whether it completed or failed, and the same result chips the task feed shows, so a rep sees the outcome without navigating anywhere.

The card leads with whatever is most useful for how the run ended, and a close control dismisses it:

  • A run that finished offers one action, straight into the output: Open Acme Corp for a single record, Open 40 accounts for a batch. One button, not a menu - the card is a prompt to go look at the work, and the reports stay a click away in the task feed.
  • A run that failed leads with See what failed, which opens the per-record breakdown on the records that errored, and keeps the link to the records beside it.
  • A run that stopped for credits leads with Run details, because that is where the resume and limit actions live, and keeps the record link beside it.
  • A run with nothing completed yet has no records to open, so it offers the two reports instead: Per-record breakdown and Run overview.

It disappears on its own after a few seconds either way, and the run stays in the task feed and in your notifications, so nothing is lost by ignoring it.

These cards only appear for a run that finishes while you have the workspace open; they are not a replay of what you missed. If the Eva chat panel is docked open, the cards sit beside it rather than behind it.

Notification settings

Section titled “Notification settings”

The workspace does not yet have a screen for configuring which notifications you receive or how they reach you. Notifications are generated automatically by the work you run, and the only controls today are reading them and marking them as read.

TODO(human): confirm whether a notification preferences screen is planned or shipped - there is currently no place in the product to choose which notifications you get or how they reach you.

What happens next

Section titled “What happens next”

Notifications arrive on their own as background work finishes; you do not refresh anything. The unread count on the bell updates live, and a new notification appears at the top of both the dropdown and the full page. Marking entries as read clears the count and removes the highlight, but the entries stay in the list so you keep the history. Click through to the linked result to act on it.

Section titled “Related”