Notifications

Vilvik keeps you in the loop with an in-app notification feed. Every page in the app has a bell icon in the top navbar; an unread count sits next to it whenever there is something new to look at. You can also choose, per event, whether you want each notification by email, in the bell, or both.

What triggers a notification¶

These are the events that can create a notification today. Each one can be turned on or off independently for the bell and for email (see the preferences section below).

Submissions¶

• Your submission finished. Fires when a run completes successfully. The notification deep-links to the submission so you can open the result in one click.
• Your submission failed. Fires when a run ends in a code error, a runtime error, or an out-of-memory kill. A clearer title is used for the out-of-memory case.
• Your submission was canceled. Fires when you (or an administrator) cancel a run that was still in flight.

Messages¶

• You received a new message. Fires when another user sends you a direct message. The notification opens the conversation directly.

Invitations¶

• Someone accepted your invitation. Fires when a person you invited to Vilvik signs up. You also receive your invitation reward at the same moment.

Billing¶

• Your subscription renewed. Fires when your monthly plan renews and a new invoice is ready.
• Your payment failed. Fires when a renewal payment attempt fails and your subscription is canceled until you fix the card. This event is always on for both channels; you cannot turn it off, because we want to make sure you can react in time.

Notifications for one user never reach another user; each row is owned by exactly one recipient.

The bell¶

Click the bell to open a dropdown with your ten most recent notifications. Unread items have a soft highlight; read items are muted. Click any item to open the related page; the notification is marked as read in the same moment.

The unread count badge updates automatically every thirty seconds without reloading the page. If you keep the tab open while a long run is finishing, the badge will go from zero to one as soon as the worker is done.

"Mark all as read"¶

There are two ways to clear the unread state:

1. From the dropdown. Click Mark all as read in the dropdown header.
2. From the full history page. Click the same button at the top right of your notifications page.

Either way, every unread item flips to read at once. The notifications themselves stay in the list; they are just not bold any more.

The full history page¶

Below the dropdown's ten most-recent entries is a Notification history link that opens the full page. It lists every notification in your account, newest first, with the timestamp of each. Older notifications stay there indefinitely so you can scroll back.

Choosing which notifications you want¶

The Notifications tab on your profile page shows every event in a grid. For each row you decide:

• whether you want the notification to land in the bell (in-app),
• whether you want the notification by email, and
• for direct messages specifically, whether you want the email always, only after a short pause if you have not read it yet, or never.

Click Save profile at the bottom to apply your choices. They take effect immediately for every future notification.

If a row in the matrix has a small lock icon next to its switch, that channel is always on by design and cannot be turned off. Today only the Payment failed row is locked, because it is the only way to alert you when access is about to lapse.

Frequently asked¶

What happens to notifications I have already received if I turn an event off? Existing rows stay where they are. The toggle only controls whether new notifications of that type are created from this moment forward.

Will I still get the navbar bell badge if I turn off the in-app channel for an event? No. Turning a channel off skips the notification entirely; it does not just hide it.

Why can I not turn off "Payment failed"? We use it to make sure you are warned when your card was declined and your subscription was canceled. There is no other channel that conveys the same urgency reliably.

Is there a single switch to pause all notifications at once? No. Every row is independent. To pause everything, set the in-app and email toggles to off on every row you can. The locked rows (only "Payment failed" today) always stay on. This is a deliberate design choice: a single master switch makes it too easy to silence your own account by accident and then miss something important.