Account and billing

Read your notifications

Open the notification bell, know what each notification means and who receives it, mark notifications as read, and know how long they stay.

The bell in the portal header collects the messages the portal sends you: a knowledge source finishing or failing, a payment succeeding or failing, a voice session ending for lack of credits. When you finish this page you will know how to read them, what each one means and who gets it, and how long they stay.

What you need

  • A signed-in portal session. Notifications are yours, not the workspace's: the same bell shows what every workspace you belong to sends you.

Steps

Step 1: Open the bell

Click the bell in the portal header. A badge on it shows how many of the notifications in the panel are unread, up to 9; from ten it reads 9+. The panel is titled Notifications and lists the 20 most recent, newest first. An unread one carries a dot and a shaded background, a read one does not, and an empty panel reads No notifications.

Step 2: Read a notification

Each row shows a title and one line of text. Click a row to mark it as read; the panel closes. Clicking does not open another page, so go to the place the notification refers to yourself: the knowledge library or the Subscription page.

New notifications appear in the panel while the portal is open, without a reload, and the panel refreshes every time you open it.

Step 3: Mark everything as read

Click Mark all as read at the top of the panel. It is enabled only while the panel holds at least one unread notification. Every notification you have, including any beyond the 20 shown, becomes read and the badge clears.

Step 4: Know what each notification means

Title When it is sent Who receives it
Document indexed A knowledge file finishes indexing and is ready for retrieval The member who uploaded it
Document failed to index A knowledge file fails to index; the text carries the reason The member who uploaded it
Web source indexed A website source finishes indexing; the text gives the page and chunk counts The member who added it
Web source failed to index A website source fails; the text carries the reason The member who added it
Voice session ended: out of credits A voice session started from the portal ends because the workspace ran out of credits The member who started it
Subscription renewed A renewal payment succeeds and the plan's credits are reset The workspace owner
Credits added A credit top-up is paid; the text gives the number of credits The workspace owner
Payment failed A subscription payment fails The workspace owner
Auto top-up turned off Auto top-up fails 3 times in a row and is switched off The workspace owner

A notification is created after the action it reports has completed, so the absence of one never means the action did not happen: check the page itself.

Worked example

Sara's policy upload finishes and Document indexed arrives with the file name and its chunk count. The bell badge shows 1. She clicks Mark all as read; the badge disappears.

What happens next

A notification stays listed for 30 days from the moment it was sent, read or not, and is then removed on its own. The panel shows the 20 most recent at any time; older ones within the 30 days are still counted by Mark all as read.

Limits

Limit Value Applies to
Notifications shown 20 most recent The bell panel
Badge count Unread notifications among the 20 shown, capped at 9+ The bell
Retention 30 days from sending, then removed automatically Every notification
Scope Per person, across every workspace they belong to The bell
Actions Mark one as read, mark all as read The bell panel

Troubleshooting

I clicked a notification and nothing opened

Clicking marks the notification as read and closes the panel; it does not navigate. Open the page it refers to from the portal's own navigation.

A notification I saw last month is gone

Notifications are removed 30 days after they are sent. The action they reported is unaffected; the source or the payment is still on its own page.

The badge shows a number but the panel looks read

The badge counts unread notifications among the 20 shown. Open the panel; it refreshes on opening and the badge follows what it shows.

I was not notified about a payment

Payment notifications go to the workspace owner only.

I uploaded a file and got no notification

Knowledge notifications go to whoever uploaded or added the source. Check the source's status in the knowledge library instead.

FAQ

Are notifications sent by email too?

No. Everything in this list appears in the bell only.

Can I delete a notification?

The panel offers Mark all as read and marking one row read by clicking it. Notifications leave on their own after 30 days.

Who gets billing notifications?

The workspace owner, whichever member made the purchase or set up auto top-up.

Does a channel call that runs out of credits notify me?

No. Voice session ended: out of credits is sent for voice sessions started from the portal, to the member who started them.

Do notifications follow the workspace I am in?

No. They are attached to your account and the bell shows all of them, whichever workspace sent them.