Manage notifications
Your notifications page lives at https://lengrowth.com/notifications.
When to use this
The page heading is Notifications, and the supporting copy says Your notification history. If there are unread items in the current view, the page also shows the unread count beside that line.
The page has two core controls:
Mark All as Read
Clickable notification cards
Each notification card shows the message text, the timestamp, and a New badge when the item has not been read yet. Read items use a quieter visual style and a check icon instead of the alert icon.
Use the notifications page when you want to:
Review all notifications in one place
Clear a backlog of unread items
Open the task, company, or other LenGrowth object mentioned in a notification
Confirm whether a message has already been read
This page is especially useful after a period away from the product. It gives you a single place to see what LenGrowth has been trying to tell you.
Step-by-step
If you are catching up after time away, the Mark All as Read button is the fastest way to clear the view.
Click Mark All as Read.
Wait for the success toast.
Confirm that the unread styling is gone from the list.
This action is helpful when you already reviewed the important items elsewhere and just want the notification center to reflect that work.
After you interact with the notification list, LenGrowth updates the read state for the items you touched. You should expect:
Unread cards to lose the New badge after they are opened
Read cards to stay in the history list without looking active
The notification list to continue acting as a historical record, not a live queue
Notifications in LenGrowth are not just passive logs. They are entry points into the part of the product that needs attention. Once you open a notification, the next step is usually to review the task, company, or workflow object it points to.
Scroll through the list carefully. The unread count reflects the items in the current view, but the cards may be easy to miss if you have many notifications.
Common problems
Wait for the page to refresh its notification history.
Scan the list from top to bottom.
Look for unread items first if you need to catch up quickly.
The page refreshes the notification history when it loads. If you are logged in and have notifications available, they appear in a single list on the page.
Find the notification card you want to open.
Read the message text.
Check the timestamp below the message.
Look for the New badge or the visual read/unread styling.
The message text is the most important part of the card. It is the part that tells you why the notification was created. The timestamp helps you understand whether it is recent or something you still need to act on.
Click the notification card.
Wait for LenGrowth to mark the item as read if it was unread.
Follow the page destination for that notification.
When you click an unread notification, LenGrowth first marks it as read and then sends you to the related route. The destination is determined by the notification type, so the page can point you to a task, a company surface, or another relevant location in the app.
If the read update fails, the page shows an error toast, but the navigation still follows the notification route. That way you can still get to the item even if the read state update is temporarily interrupted.
Make sure you clicked the card itself. The page uses the whole card as the navigation target. If the read update fails, you may still navigate, but the toast will tell you that the read action did not complete.
That is handled in settings. Use https://lengrowth.com/settings for personal notification preferences and https://lengrowth.com/settings/company for workspace-level email preferences when you are in a company context.
That usually means there is nothing in the history yet or your account has not received any notification events. The page will show No notifications found. in that case.
Related articles