Using your notifications

Where notifications live in the webapp: the profile-menu badge and unread count, the Notifications page, reading the time and labels, marking items as read, opening the related item, the empty state, and why these are in-app rather than push.

CLVR keeps your notifications in two places in the webapp: a quick count on your profile menu and a dedicated Notifications page that lists everything in full. The profile menu tells you, at a glance, that something is waiting; the page is where you read each item and act on it. This article covers both, how to read each notification, how reading works, and where a notification takes you when you select it.

The badge and unread count on your profile menu

Your profile menu opens from your avatar in the top right of the header (on a phone it slides in as a panel from the right). CLVR gives you two small signals there that something needs your attention:

• A small red dot sits on your avatar when you have one or more active notifications. It is just a signal that something is waiting: it does not show a number, and it is gone when you have nothing active.
• Inside the menu, the Notifications entry shows a red count badge with the number of active notifications you have right now. Select it to open the full page. While the count is still loading you may briefly see a small spinning icon in place of the number.

The badge counts your active notifications, which are unread updates you have not opened yet, plus items still waiting on you (notifications that ask you to do something and have not been completed, even if you have already seen them). The count reflects up to 20 active notifications and tops out there.

You do not need to reload the page to keep the count current: it refreshes automatically about every 30 seconds, and also the moment you switch back to the CLVR Benefits tab.

The Notifications page

The Notifications page is your running history in CLVR Benefits. It lists your notifications newest first, including ones you have already opened, so it works as a short history rather than only a to-do list. The page shows up to your 20 most recent notifications of any kind; anything older drops off the list. Each entry shows what happened and links you straight to the item it is about, such as an expense report.

Items that still need something from you stand out. For example, an expense report you have been asked to review shows an ACTION REQUIRED badge in orange and a Review expense report button so you can open it straight away.

Paging through your notifications

The list shows 10 notifications per page. If you have more than one page, page controls appear at the bottom so you can move between them; with a single page, no controls are shown. Your current page is kept in the page address (for example, ending in #page-2), so reloading, sharing, or bookmarking the link returns you to the same page rather than the top.

Reading the time and labels on a notification

Every notification follows the same simple layout, so you can scan your list at a glance. Each card has:

• A colored type label in the top left telling you what kind it is, such as UPDATE, ADDED AS REVIEWER, AI REVIEW, CHANGES REQUESTED, or ACTION REQUIRED. Stronger colors (orange, yellow, red, purple) mean it is new or still waiting on you; once it is read or its task is handled, the label turns gray.
• A relative time in the top right, such as 2 hours ago, 3 days ago, or just now. It counts up on its own. This relative time is shown in English even when the rest of your interface is in Swedish.
• A bold title summarising what happened, and sometimes a short gray description underneath with a little more detail.

The colored label and titles follow the language you use CLVR in, so a Swedish interface shows the Swedish label (for example UPPDATERING instead of UPDATE). Only the relative time stays in English.

Marking notifications as read

There are two ways notifications get marked as read, and nothing is deleted either way:

• Mark all as read. At the top of the page, next to the heading, a Mark all as read button with a double-check icon marks every unread notification on your account read at once. There is no per-item control.
• Automatically. CLVR also marks your notifications read whenever you leave the Notifications page, including when you navigate to another page in CLVR, switch to a different browser tab, minimise the window, or close the tab.

So in most cases, simply visiting the page and then moving on is enough to clear your unread count.

Why read notifications look faded

On the Notifications page, items you have already read are shown dimmed (faded), while unread items stay at full brightness, so you can scan the list and spot what is new at a glance. The faded look is tied to one thing only: whether the notification has been read, not whether it still needs you to do something. Move your pointer over any dimmed notification and it fades back up to full brightness while you hover, then settles back when you move away. There is no "mark as unread" option.

Why a notification can still count after you read it

The count tracks two things: notifications you have not read yet, and notifications tied to a task you have not finished. Mark all as read clears the first kind, but a notification that asks you to do something keeps counting until that task is resolved. So an item can be both faded (read) and still counted (its task is open) at the same time; that is by design, so a real task does not quietly disappear from view.

An action notification leaves your count once its task is resolved. Depending on the notification, that means opening an ADDED AS REVIEWER report and leaving your decision, opening a CHANGES REQUESTED expense and resubmitting, or (for HR users) handling an ACTION REQUIRED case. You do not always have to be the one who acts: a review notification also clears on its own if someone else finalises the report first, or if you are removed as a reviewer.

Why a review notification can disappear on its own

If an ADDED AS REVIEWER notification stops asking for your attention even though you never opened it, that is usually expected. It is never deleted; it changes from an open task to a finished one (the label turns from orange to grey, the Review expense report button is gone, and it stops counting). This happens automatically when another reviewer in your step acts first, when the report is finalised (a single decline finalises the whole report straight away), when your HR team removes you as a reviewer, or when you leave your own decision. The count is meant to show what genuinely still needs you, so clearing a settled task keeps your list honest.

Opening the item a notification is about

Most notifications link straight to the expense or page they are about, so you can act without hunting for it. A clickable notification highlights when you move your pointer over it: the background shades in and the cursor turns into a pointer. A small number are display-only and stay flat with no highlight; clicking them does nothing, which is expected, since they are there to inform you.

Where each type takes you:

• ADDED AS REVIEWER opens the expense review window right on the Notifications page, so you can leave your decision without leaving the page.
• UPDATE opens the expense it refers to, so you can see the decision a reviewer left on something you submitted.
• AI REVIEW opens the expense the AI auto-approval feature acted on.
• CHANGES REQUESTED opens the expense a reviewer asked you to fix, so you can edit and resubmit it.
• ACTION REQUIRED (about a leaving employee who has overused their allowance) opens the Employees page. You only receive this if you are on the HR side of CLVR.

Notifications appear in the app, not as push alerts

CLVR shows your notifications inside the webapp, not as phone or browser push alerts. There are no browser pop-ups and no mobile push alerts for these items today. If your tab is closed, nothing is lost: the badge and the list show whatever is waiting the next time you open CLVR.

A small number of events do send a separate email alongside the in-app notification, so you are not relying on opening the app:

• Being added as a reviewer. If you are assigned to review a colleague's expense report, you get both an in-app notification and an email.
• Submitting an expense. When you upload an expense report, you get a confirmation email alongside the report appearing under My Benefits.

Most other notifications, such as an update when a reviewer makes a decision on your own expense, are shown only in the app. The email and the in-app notification are two separate things: reading one does not clear the other.

The empty state: you have nothing to worry about

When your Notifications page has no items to list, CLVR shows a short, friendly message in the middle of the page: You have nothing to worry about! It is not an error and nothing is missing. It means you have no unread notifications and nothing pending that needs an action from you. Because read notifications normally stay in the list as a faded history, the empty message appears only when there is genuinely nothing recent left to display at all (for example, once even your read notifications have rolled off the most-recent list).

Troubleshooting

• The count did not go down after I read something. Informational notifications clear once read, but ones that need an action from you stay counted until that action is complete. Read the label: ADDED AS REVIEWER, CHANGES REQUESTED, and ACTION REQUIRED all wait for a task. Faded means read; counted means the task is still open, and both can be true at once.
• A review notification was there yesterday and now reads grey, or vanished from my count although I never touched it. Someone else finalised the report, or it was approved or declined, or you were removed as a reviewer. That is the expected behaviour, not a glitch; there is nothing left for you to do.
• The number looks out of date. Switch away and back to the tab, or wait up to 30 seconds, and it will refresh on its own.
• I see the red dot but no number. The dot only signals that something is active. Open the profile menu to see the Notifications count and the list itself.
• A notification looks faded. That just means you have already read it. Hover over it to see it clearly again. Everything looking faded usually just means you have already opened the page.
• The page controls are missing. They only appear when you have more than one page of notifications.
• Nothing happens when I click a notification. That notification is display-only. Check whether it highlights on hover: no highlight means there is nowhere to open. An ADDED AS REVIEWER item opens its review window over the page on purpose, so the list stays behind it; close the window to return.
• An older notification is gone. CLVR keeps only your 20 most recent notifications, so once newer ones arrive the oldest drop off the list and stop counting. There is nothing to recover. A missing notification almost always pointed at something you can still open directly, such as an expense report under My Benefits.
• I got an email but see nothing in the app. Open the Notifications page directly; the matching in-app item is there even when the badge has already been cleared.
• I expected a push notification on my phone. There are no mobile push alerts yet. Check the Notifications page in the webapp instead.
• Labels are in the wrong language. Change it under Language in your profile menu. The next notifications will use your new choice.
• I expected a notification but see the empty message. Check that the thing you were waiting on actually happened, and that you are the right recipient (a review notification only goes to the assigned reviewer). If you should have received it, ask your HR team to confirm.