Notifications

Read notifications and job progress from the bell, and choose which kinds of events reach you in the bell and by email.

Notifications tell you when something happened that you should know about: a site went down, a deploy went out, a backup failed, a teammate joined. The bell in the top bar collects them, and your notification settings decide which ones reach you and how.

Open the bell

Select the bell in the top bar. The panel has two tabs:

Notifications: the latest notifications, each with a title, a short message, and the time.
Jobs: jobs that are running, with their progress, and jobs that finished, with their result. Choose Clear finished to tidy the list, or select a job to see its details.

The number on the bell counts unread notifications and failed jobs you have not seen yet. A small dot means jobs are running. Avaloi checks for new notifications every 30 seconds while the tab is visible.

Use the arrow keys to move between the tabs, and press Escape to close the panel.

Act on a notification

Select a notification to open the page it points to.
Use the check button to mark one as read.
Choose Mark all as read to clear the rest. It skips notices marked Action needed.
Choose View all to open the full list, where you can filter by category or show unread items only.

Notices that need your action

Some notices ask you to do something, such as creating a password after you sign up with Google or GitHub. These notices:

Show at the top of the bell with an Action needed marker.
Have no check button, and Mark all as read skips them. Opening one does not mark it read.
Keep counting on the bell badge until you do the action.
Mark themselves done and read as soon as you do it.

Avaloi adds one of these notices once. If it goes missing before you finish the action, Avaloi adds it back the next time you sign in, and never adds a second copy.

Choose what you get

Open User settings, then Notification settings. The bell panel also links there at the bottom.
For each category, turn the Bell switch and the Email switch on or off.

Each change saves on its own and the page says Saved. If a change cannot be saved, Avaloi puts the switch back and tells you.

Category	Bell	Email
Site status and health	On	On
Deployments and environments	On	Off
Backups	On	On
Domains and certificates	On	On
Security	On	Always on
Billing	On	On
Usage and limits	On	On
Team and access	On	On
Support	On	On
Product news and tips	Off	Off

The table shows where each category starts. Results of jobs you start count as deployments and environments, except backup jobs (backups) and domain and certificate jobs (domains and certificates).

Settings that stay on

Security email is always on, to protect your account. The switch shows a lock.
Billing emails for a failed payment, read only mode, suspension, or scheduled deletion always go out, even with billing email off.
A notice that needs your action always shows in the bell, even when you turn the bell off for its category.
Invitations, sign in links, and password resets are not notifications. They always go by email.

Teams

Notification settings are personal. Each person on a team chooses their own, and turning a category off does not change what your teammates get.

Billing notices go to Owners, Admins, and Billing members. Each of them gets the notice by the channels they chose. Nobody can turn off the required ones, so a failed payment always reaches someone.

Notices to Avaloi staff, such as a request for a contact us add-on, do not depend on your settings.

Quick answers

I turned off a category, but a teammate still gets it. Settings are per person. Each teammate sets their own.

Why can I not turn off security email? It warns you about new sign ins, new API keys, and other changes to your account. If someone else is in your account, that email is how you find out.

Is there a daily summary email? Not yet. Emails go out as events happen.

Can an AI agent change my settings? An agent connected through MCP can read them with get_notification_preferences and change them with set_notification_preferences, as you, after you approve the change. It cannot turn off security email either.

Can I mark a notification unread again? Yes, through the API. PATCH /v1/notifications/{id} sets a notification read or unread.

Why can I not mark a notification as read? It is marked Action needed. Do the action and Avaloi marks it read for you. Through the API, PATCH /v1/notifications/{id} with read: true answers 409 (notification_requires_action) until then.

API

GET /v1/notifications: each item has important, requires_action, action_key, and resolved_at. An important notice has requires_action: true until you do the action.
PATCH /v1/notifications/{id}
GET /v1/users/me/notification-preferences: every category with your choice, or its default, and which channels are required.
PUT /v1/users/me/notification-preferences: change some categories, for example {"preferences": [{"category": "deployments", "email": true}]}. A channel you leave out keeps its value. Turning off a required channel answers 422.

These routes need a signed-in session or an MCP connection. Other API keys get 403. Each change writes an account.notification_preferences_changed entry to the activity log.

Still stuck?

Email [email protected] with your site name and what you tried, or send us a message.