---
title: "Notifications"
url: "/help/buuk/notifications"
updated: "2026-10-22T11:13:54.745Z"
---
# Notifications

Workspace activity finds you in three places: a **bell** in the dashboard top bar, occasional emails to workspace owners, and — when you connect them — your own Slack channels and webhook endpoints. Which events land where depends on the event, not on a global switch.

Every notification is a cue to look at something, never an action already taken — see [How Buuk works](./how-buuk-works).

## In the dashboard

The bell icon opens your notification center. Unread items add a count badge; pressing an item opens the page it refers to and marks it read, and **Mark all read** clears the batch. Activity you trigger yourself is not shown back to you.

- Suggestions — a new suggestion arrives, or one gets applied to an article
- AI drafts — an automated run produced a draft and it is ready for review
- Publishing — a page is created, published, or a scheduled draft goes live
- Integrations — a source connects, and each sync result, including failures
- Team — invites sent and members who joined
- Workspace — plan changes, trial reminders, a verified domain, and settings changes

## Comment mentions

When a teammate @mentions you in an article comment, the notification is addressed to you specifically. It links straight to that article and shows a snippet of the comment, so review requests do not get lost in general workspace activity.

## Email

Two kinds of email reach your inbox without configuration — both go to **workspace owners**, based on role rather than a toggle:

- Suggestion alerts, when automations generate suggestions. The email says how many, from which source, lists a few titles, and links to **Suggestions**. A quiet cap of three per workspace per day keeps a busy scan from flooding your inbox.
- A weekly docs report every Monday, with fresh doc-health and freshness scores and pending suggestions. See [Doc health and freshness](./doc-health-and-freshness).

Your personal sign-in emails — password changes, new codes, security events — are separate and follow your account, not the workspace. See [Account security](./account-security).

## Slack, webhooks, and automation runs

Each automation carries its own **Notification** choice: **Slack + draft** and **Webhook + draft** post results to those targets instead, while others stay app-only. The result is always a suggestion or a draft for review either way — see [Automations](./automations).

Publishing events have a machine channel too: you configure webhook endpoints for `article.published`, `article.updated`, and `article.archived` under **Settings → Developers**. See [Webhooks](./webhooks).

## At a glance

| Event | Who gets it | Where it lands |
| --- | --- | --- |
| New suggestion | Everyone in the workspace; owners also by email | Bell; owner email (up to 3 a day) |
| AI draft ready | Everyone in the workspace | Bell |
| Page published | Members except the publisher | Bell; your webhooks if configured |
| @mention in a comment | The person mentioned | Bell |
| Integration sync result | Everyone in the workspace | Bell |
| Monday docs report | Owners | Email |
| Automation finished | The target it chose | Slack, webhook, or the bell |

> [!NOTE]
> A draft-ready alert points at a draft, and a suggestion waits in its queue. Nothing announcing itself has published itself.

## Related

- The queue the suggestions arrive in: [Suggested updates](./suggested-updates).
- Choosing Slack or webhooks per automation: [Automations](./automations).
- Publish and archive events for your own systems: [Webhooks](./webhooks).
- Who receives the owner emails: [Members, roles, and groups](./members-roles-and-groups).